Link adaptation control field transmission for low latency

ABSTRACT

In a wireless local area network system, a station (STA) can transmit a first physical protocol data unit (PPDU) including a link adaptation control field. The link adaptation control field can include a bit indicating whether the link adaptation control field includes information related to low-latency traffic. The low-latency traffic can require a latency of less than or equal to a threshold value. The STA can be allocated resources for the low-latency traffic. The STA can transmit a second PPDU including the low-latency traffic through the resources.

BACKGROUND Technical Field

The present specification relates to a method for transmission of linkadaptation control field for low-latency in a wireless local areanetwork (WLAN) system.

Related Art

A wireless local area network (WLAN) has been improved in various ways.For example, the IEEE 802.11ax standard proposed an improvedcommunication environment using orthogonal frequency division multipleaccess (OFDMA) and downlink multi-user multiple input multiple output(DL MU MIMO) techniques.

The present specification proposes a technical feature that can beutilized in a new communication standard. For example, the newcommunication standard may be an extreme high throughput (EHT) standardwhich is currently being discussed. The EHT standard may use anincreased bandwidth, an enhanced PHY layer protocol data unit (PPDU)structure, an enhanced sequence, a hybrid automatic repeat request(HARQ) scheme, or the like, which is newly proposed. The EHT standardmay be called the IEEE 802.11be standard.

SUMMARY Technical Solutions

A method performed by a station (STA) in a wireless local area networksystem according to various embodiments may include technical featuresrelated to transmission of link adaptation control field forlow-latency. A station (STA) may transmit a first physical protocol dataunit (PPDU) including a link adaptation control field. The linkadaptation control field may include a bit indicating whether the linkadaptation control field includes information related to low-latencytraffic. The low-latency traffic may be traffic requiring a latency lessthan or equal to a threshold value. The STA may be allocated a resourcefor the low-latency traffic. The STA may transmit a second PPDUincluding the low-latency traffic via the resource.

Technical Effects

According to an example of the present specification, a link adaptationcontrol field including information related to low-latency traffic couldbe transmitted. The AP could calculate the amount of resources requiredto transmit data that the STA has based on the link adaptation controlfield. Therefore, the AP could allocate resources to the STA based onthe buffer state related to the low-latency traffic. Accordingly, theSTA can smoothly transmit traffic requiring low-latency.

According to an example of the present specification, the linkadaptation control field may include information related to a timeinterval of an uplink trigger based PPDU (UL TB PPDU) and informationrelated to a length of a UL TB PPDU. Accordingly, the AP may allow a STAhaving latency traffic to have an optimal TB PPDU interval and length.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example of a transmitting apparatus and/or receivingapparatus of the present specification.

FIG. 2 is a conceptual view illustrating the structure of a wirelesslocal area network (WLAN).

FIG. 3 illustrates a general link setup process.

FIG. 4 illustrates an example of a PPDU used in an IEEE standard.

FIG. 5 illustrates a layout of resource units (RUs) used in a band of 20MHz.

FIG. 6 illustrates a layout of RUs used in a band of 40 MHz.

FIG. 7 illustrates a layout of RUs used in a band of 80 MHz.

FIG. 8 illustrates a structure of an HE-SIG-B field.

FIG. 9 illustrates an example in which a plurality of user STAs areallocated to the same RU through a MU-MIMO scheme.

FIG. 10 illustrates an operation based on UL-MU.

FIG. 11 illustrates an example of a trigger frame.

FIG. 12 illustrates an example of a common information field of atrigger frame.

FIG. 13 illustrates an example of a subfield included in a per userinformation field.

FIG. 14 describes a technical feature of the UORA scheme.

FIG. 15 illustrates an example of a channel used/supported/definedwithin a 2.4 GHz band.

FIG. 16 illustrates an example of a channel used/supported/definedwithin a 5 GHz band.

FIG. 17 illustrates an example of a channel used/supported/definedwithin a 6 GHz band.

FIG. 18 illustrates an example of a PPDU used in the presentspecification.

FIG. 19 illustrates an example of a modified transmission device and/orreceiving device of the present specification.

FIG. 20 is a diagram illustrating an embodiment of a PPDU.

FIG. 21 is a diagram illustrating an embodiment of a PPDU, a PHY servicedata unit (PSDU), and a MAC PDU (MPDU).

FIG. 22 is a diagram illustrating an embodiment of the SIG 2030 field.

FIG. 23 is a diagram illustrating an embodiment of a MAC header.

FIG. 24 is a diagram illustrating an operation in each layer of awireless LAN system.

FIG. 25 is a diagram illustrating an example of a BSR control subfield.

FIG. 26 illustrates an example of a latency BSR subfield.

FIG. 27 is a diagram illustrating an HE link adaptation (HLA) controlfield.

FIG. 28 is a flowchart for explaining an embodiment of a STA operation.

FIG. 29 is a flowchart for explaining an embodiment of an AP operation.

DETAILED DESCRIPTION

In the present specification, “A or B” may mean “only A”, “only B” or“both A and B”. In other words, in the present specification, “A or B”may be interpreted as “A and/or B”. For example, in the presentspecification, “A, B, or C” may mean “only A”, “only B”, “only C”, or“any combination of A, B, C”.

A slash (/) or comma used in the present specification may mean“and/or”. For example, “A/B” may mean “A and/or B”. Accordingly, “A/B”may mean “only A”, “only B”, or “both A and B”. For example, “A, B, C”may mean “A, B, or C”.

In the present specification, “at least one of A and B” may mean “onlyA”, “only B”, or “both A and B”. In addition, in the presentspecification, the expression “at least one of A or B” or “at least oneof A and/or B” may be interpreted as “at least one of A and B”.

In addition, in the present specification, “at least one of A, B, and C”may mean “only A”, “only B”, “only C”, or “any combination of A, B, andC”. In addition, “at least one of A, B, or C” or “at least one of A, B,and/or C” may mean “at least one of A, B, and C”.

In addition, a parenthesis used in the present specification may mean“for example”. Specifically, when indicated as “control information(EHT-signal)”, it may mean that “EHT-signal”is proposed as an example ofthe “control information”. In other words, the “control information” ofthe present specification is not limited to “EHT-signal”, and“EHT-signal” may be proposed as an example of the “control information”.In addition, when indicated as “control information (i.e., EHT-signal)”,it may also mean that “EHT-signal” is proposed as an example of the“control information”.

Technical features described individually in one figure in the presentspecification may be individually implemented, or may be simultaneouslyimplemented.

The following example of the present specification may be applied tovarious wireless communication systems. For example, the followingexample of the present specification may be applied to a wireless localarea network (WLAN) system. For example, the present specification maybe applied to the IEEE 802.11a/g/n/ac standard or the IEEE 802.11axstandard. In addition, the present specification may also be applied tothe newly proposed EHT standard or IEEE 802.11be standard. In addition,the example of the present specification may also be applied to a newWLAN standard enhanced from the EHT standard or the IEEE 802.11bestandard. In addition, the example of the present specification may beapplied to a mobile communication system. For example, it may be appliedto a mobile communication system based on long term evolution (LTE)depending on a 3rd generation partnership project (3GPP) standard andbased on evolution of the LTE. In addition, the example of the presentspecification may be applied to a communication system of a 5G NRstandard based on the 3GPP standard.

Hereinafter, in order to describe a technical feature of the presentspecification, a technical feature applicable to the presentspecification will be described.

FIG. 1 shows an example of a transmitting apparatus and/or receivingapparatus of the present specification.

In the example of FIG. 1 , various technical features described belowmay be performed. FIG. 1 relates to at least one station (STA). Forexample, STAs 110 and 120 of the present specification may also becalled in various terms such as a mobile terminal, a wireless device, awireless transmit/receive unit (WTRU), a user equipment (UE), a mobilestation (MS), a mobile subscriber unit, or simply a user. The STAs 110and 120 of the present specification may also be called in various termssuch as a network, a base station, a node-B, an access point (AP), arepeater, a router, a relay, or the like. The STAs 110 and 120 of thepresent specification may also be referred to as various names such as areceiving apparatus, a transmitting apparatus, a receiving STA, atransmitting STA, a receiving device, a transmitting device, or thelike.

For example, the STAs 110 and 120 may serve as an AP or a non-AP. Thatis, the STAs 110 and 120 of the present specification may serve as theAP and/or the non-AP.

STAs 110 and 120 of the present specification may support variouscommunication standards together in addition to the IEEE 802.11standard. For example, a communication standard (e.g., LTE, LTE-A, 5G NRstandard) or the like based on the 3GPP standard may be supported. Inaddition, the STA of the present specification may be implemented asvarious devices such as a mobile phone, a vehicle, a personal computer,or the like. In addition, the STA of the present specification maysupport communication for various communication services such as voicecalls, video calls, data communication, and self-driving(autonomous-driving), or the like.

The STAs 110 and 120 of the present specification may include a mediumaccess control (MAC) conforming to the IEEE 802.11 standard and aphysical layer interface for a radio medium.

The STAs 110 and 120 will be described below with reference to asub-figure (a) of FIG. 1 .

The first STA 110 may include a processor 111, a memory 112, and atransceiver 113. The illustrated process, memory, and transceiver may beimplemented individually as separate chips, or at least twoblocks/functions may be implemented through a single chip.

The transceiver 113 of the first STA performs a signaltransmission/reception operation. Specifically, an IEEE 802.11 packet(e.g., IEEE 802.11a/b/g/n/ac/ax/be, etc.) may be transmitted/received.

For example, the first STA 110 may perform an operation intended by anAP. For example, the processor 111 of the AP may receive a signalthrough the transceiver 113, process a reception (RX) signal, generate atransmission (TX) signal, and provide control for signal transmission.The memory 112 of the AP may store a signal (e.g., RX signal) receivedthrough the transceiver 113, and may store a signal (e.g., TX signal) tobe transmitted through the transceiver.

For example, the second STA 120 may perform an operation intended by anon-AP STA. For example, a transceiver 123 of a non-AP performs a signaltransmission/reception operation. Specifically, an IEEE 802.11 packet(e.g., IEEE 802.11a/b/g/n/ac/ax/be packet, etc.) may betransmitted/received.

For example, a processor 121 of the non-AP STA may receive a signalthrough the transceiver 123, process an RX signal, generate a TX signal,and provide control for signal transmission. A memory 122 of the non-APSTA may store a signal (e.g., RX signal) received through thetransceiver 123, and may store a signal (e.g., TX signal) to betransmitted through the transceiver.

For example, an operation of a device indicated as an AP in thespecification described below may be performed in the first STA 110 orthe second STA 120. For example, if the first STA 110 is the AP, theoperation of the device indicated as the AP may be controlled by theprocessor 111 of the first STA 110, and a related signal may betransmitted or received through the transceiver 113 controlled by theprocessor 111 of the first STA 110. In addition, control informationrelated to the operation of the AP or a TX/RX signal of the AP may bestored in the memory 112 of the first STA 110. In addition, if thesecond STA 120 is the AP, the operation of the device indicated as theAP may be controlled by the processor 121 of the second STA 120, and arelated signal may be transmitted or received through the transceiver123 controlled by the processor 121 of the second STA 120. In addition,control information related to the operation of the AP or a TX/RX signalof the AP may be stored in the memory 122 of the second STA 120.

For example, in the specification described below, an operation of adevice indicated as a non-AP (or user-STA) may be performed in the firstSTA 110 or the second STA 120. For example, if the second STA 120 is thenon-AP, the operation of the device indicated as the non-AP may becontrolled by the processor 121 of the second STA 120, and a relatedsignal may be transmitted or received through the transceiver 123controlled by the processor 121 of the second STA 120. In addition,control information related to the operation of the non-AP or a TX/RXsignal of the non-AP may be stored in the memory 122 of the second STA120. For example, if the first STA 110 is the non-AP, the operation ofthe device indicated as the non-AP may be controlled by the processor111 of the first STA 110, and a related signal may be transmitted orreceived through the transceiver 113 controlled by the processor 111 ofthe first STA 110. In addition, control information related to theoperation of the non-AP or a TX/RX signal of the non-AP may be stored inthe memory 112 of the first STA 110.

In the specification described below, a device called a(transmitting/receiving) STA, a first STA, a second STA, a STA1, a STA2,an AP, a first AP, a second AP, an AP1, an AP2, a(transmitting/receiving) terminal, a (transmitting/receiving) device, a(transmitting/receiving) apparatus, a network, or the like may imply theSTAs 110 and 120 of FIG. 1 . For example, a device indicated as, withouta specific reference numeral, the (transmitting/receiving) STA, thefirst STA, the second STA, the STA1, the STA2, the AP, the first AP, thesecond AP, the AP1, the AP2, the (transmitting/receiving) terminal, the(transmitting/receiving) device, the (transmitting/receiving) apparatus,the network, or the like may imply the STAs 110 and 120 of FIG. 1 . Forexample, in the following example, an operation in which various STAstransmit/receive a signal (e.g., a PPDU) may be performed in thetransceivers 113 and 123 of FIG. 1 . In addition, in the followingexample, an operation in which various STAs generate a TX/RX signal orperform data processing and computation in advance for the TX/RX signalmay be performed in the processors 111 and 121 of FIG. 1 . For example,an example of an operation for generating the TX/RX signal or performingthe data processing and computation in advance may include: 1) anoperation ofdetermining/obtaining/configuring/computing/decoding/encoding bitinformation of a sub-field (SIG, STF, LTF, Data) included in a PPDU; 2)an operation of determining/configuring/obtaining a time resource orfrequency resource (e.g., a subcarrier resource) or the like used forthe sub-field (SIG, STF, LTF, Data) included the PPDU; 3) an operationof determining/configuring/obtaining a specific sequence (e.g., a pilotsequence, an STF/LTF sequence, an extra sequence applied to SIG) or thelike used for the sub-field (SIG, STF, LTF, Data) field included in thePPDU; 4) a power control operation and/or power saving operation appliedfor the STA; and 5) an operation related todetermining/obtaining/configuring/decoding/encoding or the like of anACK signal. In addition, in the following example, a variety ofinformation used by various STAs fordetermining/obtaining/configuring/computing/decoding/decoding a TX/RXsignal (e.g., information related to a field/subfield/controlfield/parameter/power or the like) may be stored in the memories 112 and122 of FIG. 1 .

The aforementioned device/STA of the sub-figure (a) of FIG. 1 may bemodified as shown in the sub-figure (b) of FIG. 1 . Hereinafter, theSTAs 110 and 120 of the present specification will be described based onthe sub-figure (b) of FIG. 1 .

For example, the transceivers 113 and 123 illustrated in the sub-figure(b) of FIG. 1 may perform the same function as the aforementionedtransceiver illustrated in the sub-figure (a) of FIG. 1 . For example,processing chips 114 and 124 illustrated in the sub-figure (b) of FIG. 1may include the processors 111 and 121 and the memories 112 and 122. Theprocessors 111 and 121 and memories 112 and 122 illustrated in thesub-figure (b) of FIG. 1 may perform the same function as theaforementioned processors 111 and 121 and memories 112 and 122illustrated in the sub-figure (a) of FIG. 1 .

A mobile terminal, a wireless device, a wireless transmit/receive unit(WTRU), a user equipment (UE), a mobile station (MS), a mobilesubscriber unit, a user, a user STA, a network, a base station, aNode-B, an access point (AP), a repeater, a router, a relay, a receivingunit, a transmitting unit, a receiving STA, a transmitting STA, areceiving device, a transmitting device, a receiving apparatus, and/or atransmitting apparatus, which are described below, may imply the STAs110 and 120 illustrated in the sub-figure (a)/(b) of FIG. 1 , or mayimply the processing chips 114 and 124 illustrated in the sub-figure (b)of FIG. 1 . That is, a technical feature of the present specificationmay be performed in the STAs 110 and 120 illustrated in the sub-figure(a)/(b) of FIG. 1 , or may be performed only in the processing chips 114and 124 illustrated in the sub-figure (b) of FIG. 1 . For example, atechnical feature in which the transmitting STA transmits a controlsignal may be understood as a technical feature in which a controlsignal generated in the processors 111 and 121 illustrated in thesub-figure (a)/(b) of FIG. 1 is transmitted through the transceivers 113and 123 illustrated in the sub-figure (a)/(b) of FIG. 1 . Alternatively,the technical feature in which the transmitting STA transmits thecontrol signal may be understood as a technical feature in which thecontrol signal to be transferred to the transceivers 113 and 123 isgenerated in the processing chips 114 and 124 illustrated in thesub-figure (b) of FIG. 1 .

For example, a technical feature in which the receiving STA receives thecontrol signal may be understood as a technical feature in which thecontrol signal is received by means of the transceivers 113 and 123illustrated in the sub-figure (a) of FIG. 1 . Alternatively, thetechnical feature in which the receiving STA receives the control signalmay be understood as the technical feature in which the control signalreceived in the transceivers 113 and 123 illustrated in the sub-figure(a) of FIG. 1 is obtained by the processors 111 and 121 illustrated inthe sub-figure (a) of FIG. 1 . Alternatively, the technical feature inwhich the receiving STA receives the control signal may be understood asthe technical feature in which the control signal received in thetransceivers 113 and 123 illustrated in the sub-figure (b) of FIG. 1 isobtained by the processing chips 114 and 124 illustrated in thesub-figure (b) of FIG. 1 .

Referring to the sub-figure (b) of FIG. 1 , software codes 115 and 125may be included in the memories 112 and 122. The software codes 115 and126 may include instructions for controlling an operation of theprocessors 111 and 121. The software codes 115 and 125 may be includedas various programming languages.

The processors 111 and 121 or processing chips 114 and 124 of FIG. 1 mayinclude an application-specific integrated circuit (ASIC), otherchipsets, a logic circuit and/or a data processing device. The processormay be an application processor (AP). For example, the processors 111and 121 or processing chips 114 and 124 of FIG. 1 may include at leastone of a digital signal processor (DSP), a central processing unit(CPU), a graphics processing unit (GPU), and a modulator and demodulator(modem). For example, the processors 111 and 121 or processing chips 114and 124 of FIG. 1 may be SNAPDRAGON™ series of processors made byQualcomm®, EXYNOS™ series of processors made by Samsung®, A series ofprocessors made by Apple®, HELIO™ series of processors made byMediaTek®, ATOM™ series of processors made by Intel® or processorsenhanced from these processors.

In the present specification, an uplink may imply a link forcommunication from a non-AP STA to an SP STA, and an uplinkPPDU/packet/signal or the like may be transmitted through the uplink. Inaddition, in the present specification, a downlink may imply a link forcommunication from the AP STA to the non-AP STA, and a downlinkPPDU/packet/signal or the like may be transmitted through the downlink.

FIG. 2 is a conceptual view illustrating the structure of a wirelesslocal area network (WLAN).

An upper part of FIG. 2 illustrates the structure of an infrastructurebasic service set (BSS) of institute of electrical and electronicengineers (i.e. EE) 802.11.

Referring the upper part of FIG. 2 , the wireless LAN system may includeone or more infrastructure BSSs 200 and 205 (hereinafter, referred to asBSS). The BSSs 200 and 205 as a set of an AP and a STA such as an accesspoint (AP) 225 and a station (STA1) 200-1 which are successfullysynchronized to communicate with each other are not concepts indicatinga specific region. The BSS 205 may include one or more STAs 205-1 and205-2 which may be joined to one AP 230.

The BSS may include at least one STA, APs providing a distributionservice, and a distribution system (DS) 210 connecting multiple APs.

The distribution system 210 may implement an extended service set (ESS)240 extended by connecting the multiple BSSs 200 and 205. The ESS 240may be used as a term indicating one network configured by connectingone or more APs 225 or 230 through the distribution system 210. The APincluded in one ESS 240 may have the same service set identification(SSID).

A portal 220 may serve as a bridge which connects the wireless LANnetwork (i.e. EE 802.11) and another network (e.g., 802.X).

In the BSS illustrated in the upper part of FIG. 2 , a network betweenthe APs 225 and 230 and a network between the APs 225 and 230 and theSTAs 200-1, 205-1, and 205-2 may be implemented. However, the network isconfigured even between the STAs without the APs 225 and 230 to performcommunication. A network in which the communication is performed byconfiguring the network even between the STAs without the APs 225 and230 is defined as an Ad-Hoc network or an independent basic service set(IBSS).

A lower part of FIG. 2 illustrates a conceptual view illustrating theIBSS.

Referring to the lower part of FIG. 2 , the IBSS is a BSS that operatesin an Ad-Hoc mode. Since the IBSS does not include the access point(AP), a centralized management entity that performs a managementfunction at the center does not exist. That is, in the IBSS, STAs 250-1,250-2, 250-3, 255-4, and 255-5 are managed by a distributed manner. Inthe IBSS, all STAs 250-1, 250-2, 250-3, 255-4, and 255-5 may beconstituted by movable STAs and are not permitted to access the DS toconstitute a self-contained network.

FIG. 3 illustrates a general link setup process.

In S310, a STA may perform a network discovery operation. The networkdiscovery operation may include a scanning operation of the STA. Thatis, to access a network, the STA needs to discover a participatingnetwork. The STA needs to identify a compatible network beforeparticipating in a wireless network, and a process of identifying anetwork present in a particular area is referred to as scanning Scanningmethods include active scanning and passive scanning.

FIG. 3 illustrates a network discovery operation including an activescanning process. In active scanning, a STA performing scanningtransmits a probe request frame and waits for a response to the proberequest frame in order to identify which AP is present around whilemoving to channels. A responder transmits a probe response frame as aresponse to the probe request frame to the STA having transmitted theprobe request frame. Here, the responder may be a STA that transmits thelast beacon frame in a BSS of a channel being scanned. In the BSS, sincean AP transmits a beacon frame, the AP is the responder. In an IBSS,since STAs in the IBSS transmit a beacon frame in turns, the responderis not fixed. For example, when the STA transmits a probe request framevia channel 1 and receives a probe response frame via channel 1, the STAmay store BSS-related information included in the received proberesponse frame, may move to the next channel (e.g., channel 2), and mayperform scanning (e.g., transmits a probe request and receives a proberesponse via channel 2) by the same method.

Although not shown in FIG. 3 , scanning may be performed by a passivescanning method. In passive scanning, a STA performing scanning may waitfor a beacon frame while moving to channels. A beacon frame is one ofmanagement frames in IEEE 802.11 and is periodically transmitted toindicate the presence of a wireless network and to enable the STAperforming scanning to find the wireless network and to participate inthe wireless network. In a BSS, an AP serves to periodically transmit abeacon frame. In an IBSS, STAs in the IBSS transmit a beacon frame inturns. Upon receiving the beacon frame, the STA performing scanningstores information about a BSS included in the beacon frame and recordsbeacon frame information in each channel while moving to anotherchannel. The STA having received the beacon frame may store BSS-relatedinformation included in the received beacon frame, may move to the nextchannel, and may perform scanning in the next channel by the samemethod.

After discovering the network, the STA may perform an authenticationprocess in S320. The authentication process may be referred to as afirst authentication process to be clearly distinguished from thefollowing security setup operation in S340. The authentication processin S320 may include a process in which the STA transmits anauthentication request frame to the AP and the AP transmits anauthentication response frame to the STA in response. The authenticationframes used for an authentication request/response are managementframes.

The authentication frames may include information about anauthentication algorithm number, an authentication transaction sequencenumber, a status code, a challenge text, a robust security network(RSN), and a finite cyclic group.

The STA may transmit the authentication request frame to the AP. The APmay determine whether to allow the authentication of the STA based onthe information included in the received authentication request frame.The AP may provide the authentication processing result to the STA viathe authentication response frame.

When the STA is successfully authenticated, the STA may perform anassociation process in S330. The association process includes a processin which the STA transmits an association request frame to the AP andthe AP transmits an association response frame to the STA in response.The association request frame may include, for example, informationabout various capabilities, a beacon listen interval, a service setidentifier (SSID), a supported rate, a supported channel, RSN, amobility domain, a supported operating class, a traffic indication map(TIM) broadcast request, and an interworking service capability. Theassociation response frame may include, for example, information aboutvarious capabilities, a status code, an association ID (AID), asupported rate, an enhanced distributed channel access (EDCA) parameterset, a received channel power indicator (RCPI), a receivedsignal-to-noise indicator (RSNI), a mobility domain, a timeout interval(association comeback time), an overlapping BSS scanning parameter, aTIM broadcast response, and a QoS map.

In S340, the STA may perform a security setup process. The securitysetup process in S340 may include a process of setting up a private keythrough four-way handshaking, for example, through an extensibleauthentication protocol over LAN (EAPOL) frame.

FIG. 4 illustrates an example of a PPDU used in an IEEE standard.

As illustrated, various types of PHY protocol data units (PPDUs) areused in IEEE a/g/n/ac standards. Specifically, an LTF and a STF includea training signal, a SIG-A and a SIG-B include control information for areceiving STA, and a data field includes user data corresponding to aPSDU (MAC PDU/aggregated MAC PDU).

FIG. 4 also includes an example of an HE PPDU according to IEEE802.11ax. The HE PPDU according to FIG. 4 is an illustrative PPDU formultiple users. An HE-SIG-B may be included only in a PPDU for multipleusers, and an HE-SIG-B may be omitted in a PPDU for a single user.

As illustrated in FIG. 4 , the HE-PPDU for multiple users (MUs) mayinclude a legacy-short training field (L-STF), a legacy-long trainingfield (L-LTF), a legacy-signal (L-SIG), a high efficiency-signal A(HE-SIG A), a high efficiency-signal-B (HE-SIG B), a highefficiency-short training field (HE-STF), a high efficiency-longtraining field (HE-LTF), a data field (alternatively, an MAC payload),and a packet extension (PE) field. The respective fields may betransmitted for illustrated time periods (i.e., 4 or 8 μs).

Hereinafter, a resource unit (RU) used for a PPDU is described. An RUmay include a plurality of subcarriers (or tones). An RU may be used totransmit a signal to a plurality of STAs according to OFDMA. Further, anRU may also be defined to transmit a signal to one STA. An RU may beused for an STF, an LTF, a data field, or the like.

FIG. 5 illustrates a layout of resource units (RUs) used in a band of 20MHz.

As illustrated in FIG. 5 , resource units (RUs) corresponding todifferent numbers of tones (i.e., subcarriers) may be used to form somefields of an HE-PPDU. For example, resources may be allocated inillustrated RUs for an HE-STF, an HE-LTF, and a data field.

As illustrated in the uppermost part of FIG. 5 , a 26-unit (i.e., a unitcorresponding to 26 tones) may be disposed. Six tones may be used for aguard band in the leftmost band of the 20 MHz band, and five tones maybe used for a guard band in the rightmost band of the 20 MHz band.Further, seven DC tones may be inserted in a center band, that is, a DCband, and a 26-unit corresponding to 13 tones on each of the left andright sides of the DC band may be disposed. A 26-unit, a 52-unit, and a106-unit may be allocated to other bands. Each unit may be allocated fora receiving STA, that is, a user.

The layout of the RUs in FIG. 5 may be used not only for a multipleusers (MUs) but also for a single user (SU), in which case one 242-unitmay be used and three DC tones may be inserted as illustrated in thelowermost part of FIG. 5 .

Although FIG. 5 proposes RUs having various sizes, that is, a 26-RU, a52-RU, a 106-RU, and a 242-RU, specific sizes of RUs may be extended orincreased. Therefore, the present embodiment is not limited to thespecific size of each RU (i.e., the number of corresponding tones).

FIG. 6 illustrates a layout of RUs used in a band of 40 MHz.

Similarly to FIG. 5 in which RUs having various sizes are used, a 26-RU,a 52-RU, a 106-RU, a 242-RU, a 484-RU, and the like may be used in anexample of FIG. 6 . Further, five DC tones may be inserted in a centerfrequency, 12 tones may be used for a guard band in the leftmost band ofthe 40 MHz band, and 11 tones may be used for a guard band in therightmost band of the 40 MHz band.

As illustrated in FIG. 6 , when the layout of the RUs is used for asingle user, a 484-RU may be used. The specific number of RUs may bechanged similarly to FIG. 5 .

FIG. 7 illustrates a layout of RUs used in a band of 80 MHz.

Similarly to FIG. 5 and FIG. 6 in which RUs having various sizes areused, a 26-RU, a 52-RU, a 106-RU, a 242-RU, a 484-RU, a 996-RU, and thelike may be used in an example of FIG. 7 . Further, seven DC tones maybe inserted in the center frequency, 12 tones may be used for a guardband in the leftmost band of the 80 MHz band, and 11 tones may be usedfor a guard band in the rightmost band of the 80 MHz band. In addition,a 26-RU corresponding to 13 tones on each of the left and right sides ofthe DC band may be used.

As illustrated in FIG. 7 , when the layout of the RUs is used for asingle user, a 996-RU may be used, in which case five DC tones may beinserted.

In the meantime, the fact that the specific number of RUs can be changedis the same as those of FIGS. 5 and 6 .

The RU arrangement (i.e., RU location) shown in FIGS. 5 to 7 can beapplied to a new wireless LAN system (e.g. EHT system) as it is.Meanwhile, for the 160 MHz band supported by the new WLAN system, the RUarrangement for 80 MHz (i.e., an example of FIG. 7 ) may be repeatedtwice, or the RU arrangement for the 40 MHz (i.e., an example of FIG. 6) may be repeated 4 times. In addition, when the EHT PPDU is configuredfor the 320 MHz band, the arrangement of the RU for 80 MHz (i.e., anexample of FIG. 7 ) may be repeated 4 times or the arrangement of the RUfor 40 MHz (i.e., an example of FIG. 6 ) may be repeated 8 times.

One RU of the present specification may be allocated for a single STA(e.g., a single non-AP STA). Alternatively, a plurality of RUs may beallocated for one STA (e.g., a non-AP STA).

The RU described in the present specification may be used in uplink (UL)communication and downlink (DL) communication. For example, when UL-MUcommunication which is solicited by a trigger frame is performed, atransmitting STA (e.g., an AP) may allocate a first RU (e.g.,26/52/106/242-RU, etc.) to a first STA through the trigger frame, andmay allocate a second RU (e.g., 26/52/106/242-RU, etc.) to a second STA.Thereafter, the first STA may transmit a first trigger-based PPDU basedon the first RU, and the second STA may transmit a second trigger-basedPPDU based on the second RU. The first/second trigger-based PPDU istransmitted to the AP at the same (or overlapped) time period.

For example, when a DL MU PPDU is configured, the transmitting STA(e.g., AP) may allocate the first RU (e.g., 26/52/106/242-RU. etc.) tothe first STA, and may allocate the second RU (e.g., 26/52/106/242-RU,etc.) to the second STA. That is, the transmitting STA (e.g., AP) maytransmit HE-STF, HE-LTF, and Data fields for the first STA through thefirst RU in one MU PPDU, and may transmit HE-STF, HE-LTF, and Datafields for the second STA through the second RU.

Information related to a layout of the RU may be signaled throughHE-SIG-B.

FIG. 8 illustrates a structure of an HE-SIG-B field.

As illustrated, an HE-SIG-B field 810 includes a common field 820 and auser-specific field 830. The common field 820 may include informationcommonly applied to all users (i.e., user STAs) which receive SIG-B. Theuser-specific field 830 may be called a user-specific control field.When the SIG-B is transferred to a plurality of users, the user-specificfield 830 may be applied only any one of the plurality of users.

As illustrated in FIG. 8 , the common field 820 and the user-specificfield 830 may be separately encoded.

The common field 820 may include RU allocation information of N*8 bits.For example, the RU allocation information may include informationrelated to a location of an RU. For example, when a 20 MHz channel isused as shown in FIG. 5 , the RU allocation information may includeinformation related to a specific frequency band to which a specific RU(26-RU/52-RU/106-RU) is arranged.

An example of a case in which the RU allocation information consists of8 bits is as follows.

TABLE 1 8 bits indices (B7 B6 B5 B4 Number B3 B2 B1 B0) #1 #2 #3 #4 #5#6 #7 #8 #9 of entries 00000000 26 26 26 26 26 26 26 26 26 1 00000001 2626 26 26 26 26 26 52 1 00000010 26 26 26 26 26 52 26 26 1 00000011 26 2626 26 26 52 52 1 00000100 26 26 52 26 26 26 26 26 1 00000101 26 26 52 2626 26 52 1 00000110 26 26 52 26 52 26 26 1 00000111 26 26 52 26 52 52 100001000 52 26 26 26 26 26 26 26 1

As shown the example of FIG. 5 , up to nine 26-RUs may be allocated tothe 20 MHz channel. When the RU allocation information of the commonfield 820 is set to “00000000” as shown in Table 1, the nine 26-RUs maybe allocated to a corresponding channel (i.e., 20 MHz). In addition,when the RU allocation information of the common field 820 is set to“00000001” as shown in Table 1, seven 26-RUs and one 52-RU are arrangedin a corresponding channel. That is, in the example of FIG. 5 , the52-RU may be allocated to the rightmost side, and the seven 26-RUs maybe allocated to the left thereof.

The example of Table 1 shows only some of RU locations capable ofdisplaying the RU allocation information.

For example, the RU allocation information may include an example ofTable 2 below.

TABLE 2 8 bits indices (B7 B6 B5 B4 Number B3 B2 B1 B0) #1 #2 #3 #4 #5#6 #7 #8 #9 of entries 01000y₂y₁y₀ 106 26 26 26 26 26 8 01001y₂y₁y₀ 10626 26 26 52 8

“01000y2y1y0” relates to an example in which a 106-RU is allocated tothe leftmost side of the 20 MHz channel, and five 26-RUs are allocatedto the right side thereof. In this case, a plurality of STAs (e.g.,user-STAs) may be allocated to the 106-RU, based on a MU-MIMO scheme.Specifically, up to 8 STAs (e.g., user-STAs) may be allocated to the106-RU, and the number of STAs (e.g., user-STAs) allocated to the 106-RUis determined based on 3-bit information (y2y1y0). For example, when the3-bit information (y2y1y0) is set to N, the number of STAs (e.g.,user-STAs) allocated to the 106-RU based on the MU-MIMO scheme may beN+1.

In general, a plurality of STAs (e.g., user STAs) different from eachother may be allocated to a plurality of RUs. However, the plurality ofSTAs (e.g., user STAs) may be allocated to one or more RUs having atleast a specific size (e.g., 106 subcarriers), based on the MU-MIMOscheme.

As shown in FIG. 8 , the user-specific field 830 may include a pluralityof user fields. As described above, the number of STAs (e.g., user STAs)allocated to a specific channel may be determined based on the RUallocation information of the common field 820. For example, when the RUallocation information of the common field 820 is “00000000”, one userSTA may be allocated to each of nine 26-RUs (e.g., nine user STAs may beallocated). That is, up to 9 user STAs may be allocated to a specificchannel through an OFDMA scheme. In other words, up to 9 user STAs maybe allocated to a specific channel through a non-MU-MIMO scheme.

For example, when RU allocation is set to “01000y2y1y0”, a plurality ofSTAs may be allocated to the 106-RU arranged at the leftmost sidethrough the MU-MIMO scheme, and five user STAs may be allocated to five26-RUs arranged to the right side thereof through the non-MU MIMOscheme. This case is specified through an example of FIG. 9 .

FIG. 9 illustrates an example in which a plurality of user STAs areallocated to the same RU through a MU-MIMO scheme.

For example, when RU allocation is set to “01000010” as shown in FIG. 9, a 106-RU may be allocated to the leftmost side of a specific channel,and five 26-RUs may be allocated to the right side thereof. In addition,three user STAs may be allocated to the 106-RU through the MU-MIMOscheme. As a result, since eight user STAs are allocated, theuser-specific field 830 of HE-SIG-B may include eight user fields.

The eight user fields may be expressed in the order shown in FIG. 9 . Inaddition, as shown in FIG. 8 , two user fields may be implemented withone user block field.

The user fields shown in FIG. 8 and FIG. 9 may be configured based ontwo formats. That is, a user field related to a MU-MIMO scheme may beconfigured in a first format, and a user field related to a non-MIMOscheme may be configured in a second format. Referring to the example ofFIG. 9 , a user field 1 to a user field 3 may be based on the firstformat, and a user field 4 to a user field 8 may be based on the secondformat. The first format or the second format may include bitinformation of the same length (e.g., 21 bits).

Each user field may have the same size (e.g., 21 bits). For example, theuser field of the first format (the first of the MU-MIMO scheme) may beconfigured as follows.

For example, a first bit (i.e., B0-B10) in the user field (i.e., 21bits) may include identification information (e.g., STA-ID, partial AID,etc.) of a user STA to which a corresponding user field is allocated. Inaddition, a second bit (i.e., B11-B14) in the user field (i.e., 21 bits)may include information related to a spatial configuration.Specifically, an example of the second bit (i.e., B11-B14) may be asshown in Table 3 and Table 4 below.

TABLE 3 N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS)Total Number N_(user) B3 . . . B0 [1] [2] [3] [4] [5] [6] [7] [8]N_(STS) of entries 2 0000-0011 1-4 1 2-5 10 0100-0110 2-4 2 4-50111-1000 3-4 3 6-7 1001 4 4 8 3 0000-0011 1-4 1 1 3-6 13 0100-0110 2-42 1 5-7 0111-1000 3-4 3 1 7-8 1001-1011 2-4 2 2 6-8 1100 3 3 2 8 40000-0011 1-4 1 1 1 4-7 11 0100-0110 2-4 2 1 1 6-8 0111 3 3 1 1 81000-1001 2-3 2 2 1 7-8 1010 2 2 2 2 8

TABLE 4 N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS)Total Number N_(user) B3 . . . B0 [1] [2] [3] [4] [5] [6] [7] [8]N_(STS) of entries 5 0000-0011 1-4 1 1 1 1 5-8 7 0100-0101 2-3 2 1 1 17-8 0110 2 2 2 1 1 8 6 0000-0010 1-3 1 1 1 1 1 6-8 4 0011 2 2 1 1 1 1 87 0000-0001 1-2 1 1 1 1 1 1 7-8 2 8 0000 1 1 1 1 1 1 1 1 8 1

As shown in Table 3 and/or Table 4, the second bit (e.g., B11-B14) mayinclude information related to the number of spatial streams allocatedto the plurality of user STAs which are allocated based on the MU-MIMOscheme. For example, when three user STAs are allocated to the 106-RUbased on the MU-MIMO scheme as shown in FIG. 9 , N_user is set to “3”.Therefore, values of N_STS[1], N_STS[2], and N_STS[3] may be determinedas shown in Table 3. For example, when a value of the second bit(B11-B14) is “0011”, it may be set to N_STS[1]=4, N_STS[2]=1,N_STS[3]=1. That is, in the example of FIG. 9 , four spatial streams maybe allocated to the user field 1, one spatial stream may be allocated tothe user field 1, and one spatial stream may be allocated to the userfield 3.

As shown in the example of Table 3 and/or Table 4, information (i.e.,the second bit, B11-B14) related to the number of spatial streams forthe user STA may consist of 4 bits. In addition, the information (i.e.,the second bit, B11-B14) on the number of spatial streams for the userSTA may support up to eight spatial streams. In addition, theinformation (i.e., the second bit, B11-B14) on the number of spatialstreams for the user STA may support up to four spatial streams for oneuser STA.

In addition, a third bit (i.e., B15-18) in the user field (i.e., 21bits) may include modulation and coding scheme (MCS) information. TheMCS information may be applied to a data field in a PPDU includingcorresponding SIG-B.

An MCS, MCS information, an MCS index, an MCS field, or the like used inthe present specification may be indicated by an index value. Forexample, the MCS information may be indicated by an index 0 to an index11. The MCS information may include information related to aconstellation modulation type (e.g., BPSK, QPSK, 16-QAM, 64-QAM,256-QAM, 1024-QAM, etc.) and information related to a coding rate (e.g.,½, ⅔, ¾, ⅚e, etc.). Information related to a channel coding type (e.g.,LCC or LDPC) may be excluded in the MCS information.

In addition, a fourth bit (i.e., B19) in the user field (i.e., 21 bits)may be a reserved field.

In addition, a fifth bit (i.e., B20) in the user field (i.e., 21 bits)may include information related to a coding type (e.g., BCC or LDPC).That is, the fifth bit (i.e., B20) may include information related to atype (e.g., BCC or LDPC) of channel coding applied to the data field inthe PPDU including the corresponding SIG-B.

The aforementioned example relates to the user field of the first format(the format of the MU-MIMO scheme). An example of the user field of thesecond format (the format of the non-MU-MIMO scheme) is as follows.

A first bit (e.g., B0-B10) in the user field of the second format mayinclude identification information of a user STA. In addition, a secondbit (e.g., B11-B13) in the user field of the second format may includeinformation related to the number of spatial streams applied to acorresponding RU. In addition, a third bit (e.g., B14) in the user fieldof the second format may include information related to whether abeamforming steering matrix is applied. A fourth bit (e.g., B15-B18) inthe user field of the second format may include modulation and codingscheme (MCS) information. In addition, a fifth bit (e.g., B19) in theuser field of the second format may include information related towhether dual carrier modulation (DCM) is applied. In addition, a sixthbit (i.e., B20) in the user field of the second format may includeinformation related to a coding type (e.g., BCC or LDPC).

FIG. 10 illustrates an operation based on UL-MU. As illustrated, atransmitting STA (e.g., an AP) may perform channel access throughcontending (e.g., a backoff operation), and may transmit a trigger frame1030. That is, the transmitting STA may transmit a PPDU including thetrigger frame 1030. Upon receiving the PPDU including the trigger frame,a trigger-based (TB) PPDU is transmitted after a delay corresponding toSIFS.

TB PPDUs 1041 and 1042 may be transmitted at the same time period, andmay be transmitted from a plurality of STAs (e.g., user STAs) havingAIDs indicated in the trigger frame 1030. An ACK frame 1050 for the TBPPDU may be implemented in various forms.

A specific feature of the trigger frame is described with reference toFIG. 11 to FIG. 13 . Even if UL-MU communication is used, an orthogonalfrequency division multiple access (OFDMA) scheme or a MU MIMO schememay be used, and the OFDMA and MU-MIMO schemes may be simultaneouslyused.

FIG. 11 illustrates an example of a trigger frame. The trigger frame ofFIG. 11 allocates a resource for uplink multiple-user (MU) transmission,and may be transmitted, for example, from an AP. The trigger frame maybe configured of a MAC frame, and may be included in a PPDU.

Each field shown in FIG. 11 may be partially omitted, and another fieldmay be added. In addition, a length of each field may be changed to bedifferent from that shown in the figure.

A frame control field 1110 of FIG. 11 may include information related toa MAC protocol version and extra additional control information. Aduration field 1120 may include time information for NAV configurationor information related to an identifier (e.g., AID) of a STA.

In addition, an RA field 1130 may include address information of areceiving STA of a corresponding trigger frame, and may be optionallyomitted. A TA field 1140 may include address information of a STA (e.g.,an AP) which transmits the corresponding trigger frame. A commoninformation field 1150 includes common control information applied tothe receiving STA which receives the corresponding trigger frame. Forexample, a field indicating a length of an L-SIG field of an uplink PPDUtransmitted in response to the corresponding trigger frame orinformation for controlling content of a SIG-A field (i.e., HE-SIG-Afield) of the uplink PPDU transmitted in response to the correspondingtrigger frame may be included. In addition, as common controlinformation, information related to a length of a CP of the uplink PPDUtransmitted in response to the corresponding trigger frame orinformation related to a length of an LTF field may be included.

In addition, per user information fields 1160#1 to 1160#N correspondingto the number of receiving STAs which receive the trigger frame of FIG.11 are preferably included. The per user information field may also becalled an “allocation field”.

In addition, the trigger frame of FIG. 11 may include a padding field1170 and a frame check sequence field 1180.

Each of the per user information fields 1160#1 to 1160#N shown in FIG.11 may include a plurality of subfields.

FIG. 12 illustrates an example of a common information field of atrigger frame. A subfield of FIG. 12 may be partially omitted, and anextra subfield may be added. In addition, a length of each subfieldillustrated may be changed.

A length field 1210 illustrated has the same value as a length field ofan L-SIG field of an uplink PPDU transmitted in response to acorresponding trigger frame, and a length field of the L-SIG field ofthe uplink PPDU indicates a length of the uplink PPDU. As a result, thelength field 1210 of the trigger frame may be used to indicate thelength of the corresponding uplink PPDU.

In addition, a cascade identifier field 1220 indicates whether a cascadeoperation is performed. The cascade operation implies that downlink MUtransmission and uplink MU transmission are performed together in thesame TXOP. That is, it implies that downlink MU transmission isperformed and thereafter uplink MU transmission is performed after apre-set time (e.g., SIFS). During the cascade operation, only onetransmitting device (e.g., AP) may perform downlink communication, and aplurality of transmitting devices (e.g., non-APs) may perform uplinkcommunication.

A CS request field 1230 indicates whether a wireless medium state or aNAV or the like is necessarily considered in a situation where areceiving device which has received a corresponding trigger frametransmits a corresponding uplink PPDU.

An HE-SIG-A information field 1240 may include information forcontrolling content of a SIG-A field (i.e., HE-SIG-A field) of theuplink PPDU in response to the corresponding trigger frame.

A CP and LTF type field 1250 may include information related to a CPlength and LTF length of the uplink PPDU transmitted in response to thecorresponding trigger frame. A trigger type field 1260 may indicate apurpose of using the corresponding trigger frame, for example, typicaltriggering, triggering for beamforming, a request for block ACK/NACK, orthe like.

It may be assumed that the trigger type field 1260 of the trigger framein the present specification indicates a trigger frame of a basic typefor typical triggering. For example, the trigger frame of the basic typemay be referred to as a basic trigger frame.

FIG. 13 illustrates an example of a subfield included in a per userinformation field. A user information field 1300 of FIG. 13 may beunderstood as any one of the per user information fields 1160#1 to1160#N mentioned above with reference to FIG. 11 . A subfield includedin the user information field 1300 of FIG. 13 may be partially omitted,and an extra subfield may be added. In addition, a length of eachsubfield illustrated may be changed.

A user identifier field 1310 of FIG. 13 indicates an identifier of a STA(i.e., receiving STA) corresponding to per user information. An exampleof the identifier may be the entirety or part of an associationidentifier (AID) value of the receiving STA.

In addition, an RU allocation field 1320 may be included. That is, whenthe receiving STA identified through the user identifier field 1310transmits a TB PPDU in response to the trigger frame, the TB PPDU istransmitted through an RU indicated by the RU allocation field 1320. Inthis case, the RU indicated by the RU allocation field 1320 may be an RUshown in FIG. 5 , FIG. 6 , and FIG. 7 .

The subfield of FIG. 13 may include a coding type field 1330. The codingtype field 1330 may indicate a coding type of the TB PPDU. For example,when BCC coding is applied to the TB PPDU, the coding type field 1330may be set to ‘1’, and when LDPC coding is applied, the coding typefield 1330 may be set to ‘0’.

In addition, the subfield of FIG. 13 may include an MCS field 1340. TheMCS field 1340 may indicate an MCS scheme applied to the TB PPDU. Forexample, when BCC coding is applied to the TB PPDU, the coding typefield 1330 may be set to ‘1’, and when LDPC coding is applied, thecoding type field 1330 may be set to ‘0’.

Hereinafter, a UL 01-DMA-based random access (UORA) scheme will bedescribed.

FIG. 14 describes a technical feature of the UORA scheme.

A transmitting STA (e.g., an AP) may allocate six RU resources through atrigger frame as shown in FIG. 14 . Specifically, the AP may allocate a1st RU resource (AID 0, RU 1), a 2nd RU resource (AID 0, RU 2), a 3rd RUresource (AID 0, RU 3), a 4th RU resource (AID 2045, RU 4), a 5th RUresource (AID 2045, RU 5), and a 6th RU resource (AID 3, RU 6).Information related to the AID 0, AID 3, or AID 2045 may be included,for example, in the user identifier field 1310 of FIG. 13 . Informationrelated to the RU 1 to RU 6 may be included, for example, in the RUallocation field 1320 of FIG. 13 . AID=0 may imply a UORA resource foran associated STA, and AID=2045 may imply a UORA resource for anun-associated STA. Accordingly, the 1st to 3rd RU resources of FIG. 14may be used as a UORA resource for the associated STA, the 4th and 5thRU resources of FIG. 14 may be used as a UORA resource for theun-associated STA, and the 6th RU resource of FIG. 14 may be used as atypical resource for UL MU.

In the example of FIG. 14 , an OFDMA random access backoff (OBO) of aSTA1 is decreased to 0, and the STA1 randomly selects the 2nd RUresource (AID 0, RU 2). In addition, since an OB0 counter of a STA⅔ isgreater than 0, an uplink resource is not allocated to the STA⅔. Inaddition, regarding a STA4 in FIG. 14 , since an AID (e.g., AID=3) ofthe STA4 is included in a trigger frame, a resource of the RU 6 isallocated without backoff.

Specifically, since the STA1 of FIG. 14 is an associated STA, the totalnumber of eligible RA RUs for the STA1 is 3 (RU 1, RU 2, and RU 3), andthus the STA1 decreases an OB0 counter by 3 so that the OB0 counterbecomes 0. In addition, since the STA2 of FIG. 14 is an associated STA,the total number of eligible RA RUs for the STA2 is 3 (RU 1, RU 2, andRU 3), and thus the STA2 decreases the OB0 counter by 3 but the OB0counter is greater than 0. In addition, since the STA3 of FIG. 14 is anun-associated STA, the total number of eligible RA RUs for the STA3 is 2(RU 4, RU 5), and thus the STA3 decreases the OB0 counter by 2 but theOB0 counter is greater than 0.

FIG. 15 illustrates an example of a channel used/supported/definedwithin a 2.4 GHz band.

The 2.4 GHz band may be called in other terms such as a first band. Inaddition, the 2.4 GHz band may imply a frequency domain in whichchannels of which a center frequency is close to 2.4 GHz (e.g., channelsof which a center frequency is located within 2.4 to 2.5 GHz) areused/supported/defined.

A plurality of 20 MHz channels may be included in the 2.4 GHz band. 20MHz within the 2.4 GHz may have a plurality of channel indices (e.g., anindex 1 to an index 14). For example, a center frequency of a 20 MHzchannel to which a channel index 1 is allocated may be 2.412 GHz, acenter frequency of a 20 MHz channel to which a channel index 2 isallocated may be 2.417 GHz, and a center frequency of a 20 MHz channelto which a channel index N is allocated may be (2.407+0.005*N) GHz. Thechannel index may be called in various terms such as a channel number orthe like. Specific numerical values of the channel index and centerfrequency may be changed.

FIG. 15 exemplifies 4 channels within a 2.4 GHz band. Each of 1st to 4thfrequency domains 1510 to 1540 shown herein may include one channel. Forexample, the 1st frequency domain 1510 may include a channel 1 (a 20 MHzchannel having an index 1). In this case, a center frequency of thechannel 1 may be set to 2412 MHz. The 2nd frequency domain 1520 mayinclude a channel 6. In this case, a center frequency of the channel 6may be set to 2437 MHz. The 3rd frequency domain 1530 may include achannel 11. In this case, a center frequency of the channel 11 may beset to 2462 MHz. The 4th frequency domain 1540 may include a channel 14.In this case, a center frequency of the channel 14 may be set to 2484MHz.

FIG. 16 illustrates an example of a channel used/supported/definedwithin a 5 GHz band.

The 5 GHz band may be called in other terms such as a second band or thelike. The 5 GHz band may imply a frequency domain in which channels ofwhich a center frequency is greater than or equal to 5 GHz and less than6 GHz (or less than 5.9 GHz) are used/supported/defined. Alternatively,the 5 GHz band may include a plurality of channels between 4.5 GHz and5.5 GHz. A specific numerical value shown in FIG. 16 may be changed.

A plurality of channels within the 5 GHz band include an unlicensednational information infrastructure (UNII)-1, a UNII-2, a UNII-3, and anISM. The INII-1 may be called UNII Low. The UNII-2 may include afrequency domain called UNII Mid and UNII-2Extended. The UNII-3 may becalled UNII-Upper.

A plurality of channels may be configured within the 5 GHz band, and abandwidth of each channel may be variously set to, for example, 20 MHz,40 MHz, 80 MHz, 160 MHz, or the like. For example, 5170 MHz to 5330 MHzfrequency domains/ranges within the UNII-1 and UNII-2 may be dividedinto eight 20 MHz channels. The 5170 MHz to 5330 MHz frequencydomains/ranges may be divided into four channels through a 40 MHzfrequency domain. The 5170 MHz to 5330 MHz frequency domains/ranges maybe divided into two channels through an 80 MHz frequency domain.Alternatively, the 5170 MHz to 5330 MHz frequency domains/ranges may bedivided into one channel through a 160 MHz frequency domain.

FIG. 17 illustrates an example of a channel used/supported/definedwithin a 6 GHz band.

The 6 GHz band may be called in other terms such as a third band or thelike. The 6 GHz band may imply a frequency domain in which channels ofwhich a center frequency is greater than or equal to 5.9 GHz areused/supported/defined. A specific numerical value shown in FIG. 17 maybe changed.

For example, the 20 MHz channel of FIG. 17 may be defined starting from5.940 GHz. Specifically, among 20 MHz channels of FIG. 17 , the leftmostchannel may have an index 1 (or a channel index, a channel number,etc.), and 5.945 GHz may be assigned as a center frequency. That is, acenter frequency of a channel of an index N may be determined as(5.940+0.005*N) GHz.

Accordingly, an index (or channel number) of the 2 MHz channel of FIG.17 may be 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61,65, 69, 73, 77, 81, 85, 89, 93, 97, 101, 105, 109, 113, 117, 121, 125,129, 133, 137, 141, 145, 149, 153, 157, 161, 165, 169, 173, 177, 181,185, 189, 193, 197, 201, 205, 209, 213, 217, 221, 225, 229, 233. Inaddition, according to the aforementioned (5.940+0.005*N)GHz rule, anindex of the 40 MHz channel of FIG. 17 may be 3, 11, 19, 27, 35, 43, 51,59, 67, 75, 83, 91, 99, 107, 115, 123, 131, 139, 147, 155, 163, 171,179, 187, 195, 203, 211, 219, 227.

Although 20, 40, 80, and 160 MHz channels are illustrated in the exampleof FIG. 17 , a 240 MHz channel or a 320 MHz channel may be additionallyadded.

Hereinafter, a PPDU transmitted/received in a STA of the presentspecification will be described.

FIG. 18 illustrates an example of a PPDU used in the presentspecification.

The PPDU 1800 depicted in FIG. 18 may be referred to as various termssuch as an EHT PPDU, a TX PPDU, an RX PPDU, a first type or N-th typePPDU, or the like. In addition, the EHT PPDU may be used in an EHTsystem and/or a new WLAN system enhanced from the EHT system.

The subfields 1801 to 1810 depicted in FIG. 18 may be referred to asvarious terms. For example, a SIG A field 1805 may be referred to anEHT-SIG-A field, a SIG B field 1806 may be referred to an EHT-SIG-B, anSTF field 1807 may be referred to an EHT-STF field, and an LTF field1808 may be referred to an EHT-LTF.

The subcarrier spacing of the L-LTF, L-STF, L-SIG, and RL-SIG fields1801, 1802, 1803, and 1804 of FIG. 18 can be set to 312.5 kHz, and thesubcarrier spacing of the STF, LTF, and Data fields 1807, 1808, and 1809of FIG. 18 can be set to 78.125 kHz. That is, the subcarrier index ofthe L-LTF, L-STF, L-SIG, and RL-SIG fields 1801, 1802, 1803, and 1804can be expressed in unit of 312.5 kHz, and the subcarrier index of theSTF, LTF, and Data fields 1807, 1808, and 1809 can be expressed in unitof 78.125 kHz.

The SIG A and/or SIG B fields of FIG. 18 may include additional fields(e.g., a SIG C field or one control symbol, etc.). The subcarrierspacing of all or part of the SIG A and SIG B fields may be set to 312.5kHz, and the subcarrier spacing of all or part of newly-defined SIGfield(s) may be set to 312.5 kHz. Meanwhile, the subcarrier spacing fora part of the newly-defined SIG field(s) may be set to a pre-definedvalue (e.g., 312.5 kHz or 78.125 kHz).

In the PPDU of FIG. 18 , the L-LTF and the L-STF may be the same asconventional L-LTF and L-STF fields.

The L-SIG field of FIG. 18 may include, for example, bit information of24 bits. For example, the 24-bit information may include a rate field of4 bits, a reserved bit of 1 bit, a length field of 12 bits, a parity bitof 1 bit, and a tail bit of 6 bits. For example, the length field of 12bits may include information related to the number of octets of acorresponding Physical Service Data Unit (PSDU). For example, the lengthfield of 12 bits may be determined based on a type of the PPDU. Forexample, when the PPDU is a non-HT, HT, VHT PPDU or an EHT PPDU, a valueof the length field may be determined as a multiple of 3. For example,when the PPDU is an HE PPDU, the value of the length field may bedetermined as “a multiple of 3”+1 or “a multiple of 3”+2. In otherwords, for the non-HT, HT, VHT PPDI or the EHT PPDU, the value of thelength field may be determined as a multiple of 3, and for the HE PPDU,the value of the length field may be determined as “a multiple of 3”+1or “a multiple of 3”+2.

For example, the transmitting STA may apply BCC encoding based on a ½coding rate to the 24-bit information of the L-SIG field. Thereafter,the transmitting STA may obtain a BCC coding bit of 48 bits. BPSKmodulation may be applied to the 48-bit coding bit, thereby generating48 BPSK symbols. The transmitting STA may map the 48 BPSK symbols topositions except for a pilot subcarrier {subcarrier index −21, −7, +7,+21} and a DC subcarrier subcarrier index 01. As a result, the 48 BPSKsymbols may be mapped to subcarrier indices −26 to −22, −20 to −8, −6 to−1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA mayadditionally map a signal of {−1, −1, −1, 1} to a subcarrier index {−28,−27, +27, +28}. The aforementioned signal may be used for channelestimation on a frequency domain corresponding to {−28, −27, +27, +28}.

The transmitting STA may generate an RL-SIG which is identical to theL-SIG. BPSK modulation may be applied to the RL-SIG. The receiving STAmay figure out that the RX PPDU is the HE PPDU or the EHT PPDU, based onthe presence of the RL-SIG.

After RL-SIG of FIG. 18 , for example, an EHT-SIG-A or one controlsymbol may be inserted. A symbol located after the RL-SIG (i.e., theEHT-SIG-A or one control symbol in the present specification) may bereferred as various names, such as a U-SIG (Universal SIG) field.

A symbol consecutive to the RL-SIG (e.g., U-SIG) may include informationof N bits, and may include information for identifying the type of theEHT PPDU. For example, the U-SIG may be configured based on two symbols(e.g., two consecutive OFDM symbols). Each symbol (e.g., OFDM symbol)for U-SIG may have a duration of 4 μs. Each symbol of the U-SIG may beused to transmit 26-bit information. For example, each symbol of theU-SIG may be transmitted/received based on 52 data tones and 4 pilottones.

Through the U-SIG (or U-SIG field), for example, A-bit information(e.g., 52 un-coded bits) may be transmitted. A first symbol of the U-SIGmay transmit first X-bit information (e.g., 26 un-coded bits) of theA-bit information, and a second symbol of the U-SIG may transmit theremaining Y-bit information (e.g. 26 un-coded bits) of the A-bitinformation. For example, the transmitting STA may obtain 26 un-codedbits included in each U-SIG symbol. The transmitting STA may performconvolutional encoding (i.e., BCC encoding) based on a rate of R=½ togenerate 52-coded bits, and may perform interleaving on the 52-codedbits. The transmitting STA may perform BPSK modulation on theinterleaved 52-coded bits to generate 52 BPSK symbols to be allocated toeach U-SIG symbol. One U-SIG symbol may be transmitted based on 65 tones(subcarriers) from a subcarrier index −28 to a subcarrier index +28,except for a DC index 0. The 52 BPSK symbols generated by thetransmitting STA may be transmitted based on the remaining tones(subcarriers) except for pilot tones, i.e., tones −21, −7, +7, +21.

For example, the A-bit information (e.g., 52 un-coded bits) generated bythe U-SIG may include a CRC field (e.g., a field having a length of 4bits) and a tail field (e.g., a field having a length of 6 bits). TheCRC field and the tail field may be transmitted through the secondsymbol of the U-SIG. The CRC field may be generated based on 26 bitsallocated to the first symbol of the U-SIG and the remaining 16 bitsexcept for the CRC/tail fields in the second symbol, and may begenerated based on the conventional CRC calculation algorithm. Inaddition, the tail field may be used to terminate trellis of aconvolutional decoder, and may be set to, for example, “000000”.

The A-bit information (e.g., 52 un-coded bits) transmitted by the U-SIG(or U-SIG field) may be divided into version-independent bits andversion-dependent bits. For example, the version-independent bits mayhave a fixed or variable size. For example, the version-independent bitsmay be allocated only to the first symbol of the U-SIG, or theversion-independent bits may be allocated to both of the first andsecond symbols of the U-SIG. For example, the version-independent bitsand the version-dependent bits may be called in various terms such as afirst control bit, a second control bit, or the like.

For example, the version-independent bits of the U-SIG may include a PHYversion identifier of 3 bits. For example, the PHY version identifier of3 bits may include information related to a PHY version of a TX/RX PPDU.For example, a first value of the PHY version identifier of 3 bits mayindicate that the TX/RX PPDU is an EHT PPDU. In other words, when thetransmitting STA transmits the EHT PPDU, the PHY version identifier of 3bits may be set to a first value. In other words, the receiving STA maydetermine that the RX PPDU is the EHT PPDU, based on the PHY versionidentifier having the first value.

For example, the version-independent bits of the U-SIG may include aUL/DL flag field of 1 bit. A first value of the UL/DL flag field of 1bit relates to UL communication, and a second value of the UL/DL flagfield relates to DL communication.

For example, the version-independent bits of the U-SIG may includeinformation related to a TXOP length and information related to a BSScolor ID.

For example, when the EHT PPDU is classified into various types (e.g.,EHT PPDU supporting SU, EHT PPDU supporting MU, EHT PPDU related toTrigger Frame, EHT PPDU related to Extended Range transmission, etc.),information related to the type of the EHT PPDU may be included inversion-independent bits or version-dependent bits of the U-SIG.

For example, the U-SIG field includes 1) a bandwidth field includinginformation related to a bandwidth, 2) a field including informationrelated an MCS scheme applied to the SIG-B, 3) a dual subcarriermodulation in the SIG-B (i.e., an indication field including informationrelated to whether the dual subcarrier modulation) is applied, 4) afield including information related to the number of symbols used forthe SIG-B, 5) a field including information on whether the SIG-B isgenerated over the entire band, 6) a field including information relatedto a type of the LTF/STF, and/or 7) information related to a fieldindicating a length of the LTF and the CP.

The SIG-B of FIG. 18 may include the technical features of HE-SIG-Bshown in the example of FIGS. 8 to 9 as it is.

An STF of FIG. 18 may be used to improve automatic gain controlestimation in a multiple input multiple output (MIMO) environment or anOFDMA environment. An LTF of FIG. 18 may be used to estimate a channelin the MIMO environment or the 01-DMA environment.

The EHT-STF of FIG. 18 may be set in various types. For example, a firsttype of STF (e.g., 1×STF) may be generated based on a first type STFsequence in which a non-zero coefficient is arranged with an interval of16 subcarriers. An STF signal generated based on the first type STFsequence may have a period of 0.8 μs, and a periodicity signal of 0.8 μsmay be repeated 5 times to become a first type STF having a length of 4μs. For example, a second type of STF (e.g., 2×STF) may be generatedbased on a second type STF sequence in which a non-zero coefficient isarranged with an interval of 8 subcarriers. An STF signal generatedbased on the second type STF sequence may have a period of 1.6 μs, and aperiodicity signal of 1.6 μs may be repeated 5 times to become a secondtype STF having a length of 8 μs. For example, a third type of STF(e.g., 4x STF) may be generated based on a third type STF sequence inwhich a non-zero coefficient is arranged with an interval of 4subcarriers. An STF signal generated based on the third type STFsequence may have a period of 3.2 μs, and a periodicity signal of 3.2 μsmay be repeated 5 times to become a second type STF having a length of16 μs. Only some of the first to third type EHT-STF sequences may beused. In addition, the EHT-LTF field may also have first, second, andthird types (i.e., 1×, 2×, 4×LTF). For example, the first/second/thirdtype LTF field may be generated based on an LTF sequence in which anon-zero coefficient is arranged with an interval of 4/2/1 subcarriers.The first/second/third type LTF may have a time length of 3.2/6.4/12.8μs. In addition, Guard Intervals (GIs) with various lengths (e.g.,0.8/1/6/3.2 μs) may be applied to the first/second/third type LTF.

Information related to the type of STF and/or LTF (including informationrelated to GI applied to the LTF) may be included in the SIG A fieldand/or the SIG B field of FIG. 18 .

The PPDU of FIG. 18 may support various bandwidths. For example, thePPDU of FIG. 18 may have a bandwidth of 20/40/80/160/240/320 MHz. Forexample, at least one field (e.g., STF, LTF, data) of FIG. 18 may beconfigured based on RUs illustrated in FIGS. 5 to 7 , and the like. Forexample, when there is one receiving STA of the PPDU of FIG. 18 , allfields of the PPDU of FIG. 18 may occupy the entire bandwidth. Forexample, when there are multiple receiving STAs of the PPDU of FIG. 18(i.e., when MU PPDU is used), some fields (e.g., STF, LTF, data) of FIG.18 may be configured based on the RUs shown in FIGS. 5 to 7 . Forexample, the STF, LTF, and data fields for the first receiving STA ofthe PPDU may be transmitted/received through a first RU, and the STF,LTF, and data fields for the second receiving STA of the PPDU may betransmitted/received through a second RU. In this case, thelocations/positions of the first and second RUs may be determined basedon FIGS. 5 to 7 , and the like.

The PPDU of FIG. 18 may be determined (or identified) as an EHT PPDUbased on the following method.

A receiving STA may determine a type of an RX PPDU as the EHT PPDU,based on the following aspect. For example, the RX PPDU may bedetermined as the EHT PPDU: 1) when a first symbol after an L-LTF signalof the RX PPDU is a BPSK symbol; 2) when RL-SIG in which the L-SIG ofthe RX PPDU is repeated is detected; and 3) when a result of applying“modulo 3” to a value of a length field of the L-SIG of the RX PPDU isdetected as “0”. When the RX PPDU is determined as the EHT PPDU, thereceiving STA may detect a type of the EHT PPDU (e.g., anSU/MU/Trigger-based/Extended Range type), based on bit informationincluded in a symbol after the RL-SIG of FIG. 18 . In other words, thereceiving STA may determine the RX PPDU as the EHT PPDU, based on: 1) afirst symbol after an L-LTF signal, which is a BPSK symbol; 2) RL-SIGcontiguous to the L-SIG field and identical to L-SIG; 3) L-SIG includinga length field in which a result of applying “modulo 3” is set to “0”;and 4) a 3-bit PHY version identifier of the aforementioned U-SIG (e.g.,a PHY version identifier having a first value).

For example, the receiving STA may determine the type of the RX PPDU asthe EHT PPDU, based on the following aspect. For example, the RX PPDUmay be determined as the HE PPDU: 1) when a first symbol after an L-LTFsignal is a BPSK symbol; 2) when RL-SIG in which the L-SIG is repeatedis detected; and 3) when a result of applying “modulo 3” to a value of alength field of the L-SIG is detected as “1” or “2”.

For example, the receiving STA may determine the type of the RX PPDU asa non-HT, HT, and VHT PPDU, based on the following aspect. For example,the RX PPDU may be determined as the non-HT, HT, and VHT PPDU: 1) when afirst symbol after an L-LTF signal is a BPSK symbol; and 2) when RL-SIGin which L-SIG is repeated is not detected. In addition, even if thereceiving STA detects that the RL-SIG is repeated, when a result ofapplying “modulo 3” to the length value of the L-SIG is detected as “0”,the RX PPDU may be determined as the non-HT, HT, and VHT PPDU.

In the following example, a signal represented as a (TX/RX/UL/DL)signal, a (TX/RX/UL/DL) frame, a (TX/RX/UL/DL) packet, a (TX/RX/UL/DL)data unit, (TX/RX/UL/DL) data, or the like may be a signaltransmitted/received based on the PPDU of FIG. 18 . The PPDU of FIG. 18may be used to transmit/receive frames of various types. For example,the PPDU of FIG. 18 may be used for a control frame. An example of thecontrol frame may include a request to send (RTS), a clear to send(CTS), a power save-poll (PS-poll), BlockACKReq, BlockAck, a null datapacket (NDP) announcement, and a trigger frame. For example, the PPDU ofFIG. 18 may be used for a management frame. An example of the managementframe may include a beacon frame, a (re-)association request frame, a(re-)association response frame, a probe request frame, and a proberesponse frame. For example, the PPDU of FIG. 18 may be used for a dataframe. For example, the PPDU of FIG. 18 may be used to simultaneouslytransmit at least two or more of the control frame, the managementframe, and the data frame.

FIG. 19 illustrates an example of a modified transmission device and/orreceiving device of the present specification.

Each device/STA of the sub-figure (a)/(b) of FIG. 1 may be modified asshown in FIG. 19 . A transceiver 630 of FIG. 19 may be identical to thetransceivers 113 and 123 of FIG. 1 . The transceiver 630 of FIG. 19 mayinclude a receiver and a transmitter.

A processor 610 of FIG. 19 may be identical to the processors 111 and121 of FIG. 1 . Alternatively, the processor 610 of FIG. 19 may beidentical to the processing chips 114 and 124 of FIG. 1 .

A memory 620 of FIG. 19 may be identical to the memories 112 and 122 ofFIG. 1 . Alternatively, the memory 620 of FIG. 19 may be a separateexternal memory different from the memories 112 and 122 of FIG. 1 .

Referring to FIG. 19 , a power management module 611 manages power forthe processor 610 and/or the transceiver 630. A battery 612 suppliespower to the power management module 611. A display 613 outputs a resultprocessed by the processor 610. A keypad 614 receives inputs to be usedby the processor 610. The keypad 614 may be displayed on the display613. A SIM card 615 may be an integrated circuit which is used tosecurely store an international mobile subscriber identity (IMSI) andits related key, which are used to identify and authenticate subscriberson mobile telephony devices such as mobile phones and computers.

Referring to FIG. 19 , a speaker 640 may output a result related to asound processed by the processor 610. A microphone 641 may receive aninput related to a sound to be used by the processor 610.

Hereinafter, technical features applied to a physical (PHY) protocoldata unit (PPDU) and a media access control (MAC) PDU (MPDU) in awireless local area network system will be described.

FIG. 20 is a diagram illustrating an embodiment of a PPDU.

Referring to FIG. 20 , the PPDU may include STF 2010, LTF 2020, SIG2030, and DATA 2040 fields. The DATA 2040 field may include a Service2041, a PSDU 2042, a PPDU Tail 2043, and a PAD 2044 fields.

The initial portion of the PPDU may include a short training field (STF)according to the conventional legacy standard. That is, the STF 2010 maybe a conventional L-STF. The STF 2010 may be used for diversitydetection, coarse frequency/time synchronization, and the like.

An initial portion of the PPDU may include a long training field (LTF)according to a conventional legacy standard. That is, the LTF 2020 maybe a conventional L-LTF. The LTF 2020 may include a long trainingorthogonal frequency division multiplexing (OFDM) symbol. The LTF 2020may be used for fine frequency/time synchronization and channelprediction.

An initial portion of the PPDU may include a signal (SIG) fieldaccording to the conventional legacy standard. That is, the SIG 2030field may be a conventional L-SIG field.

The data field 2040 may include a SERVICE field 2041, a PHY service dataunit (PSDU) 2042, a PPDU TAIL bit 2043, and a padding bit 2044. Somebits of the SERVICE field 2041 may be used for synchronization of thedescrambler at the receiving terminal. The PSDU 2042 may correspond to aMAC protocol data unit (MPDU) defined in the MAC layer, and may includedata generated/used in a higher layer. The PPDU TAIL bit 2043 may beused to return the encoder to a 0 state. The padding bit 2044 may beused to adjust the length of the data field to a specific unit.

FIG. 21 is a diagram illustrating an embodiment of a PPDU, a PHY servicedata unit (PSDU), and a MAC PDU (MPDU).

Referring to FIG. 21 , the relationship between PPDU, PSDU, and MPDU mayvary according to WLAN standards. For example, various PHYpreambles/midambles may be added between the signal (SIG) field and thedata field of FIG. 21 . A specific numerical value (for example, thenumber of bits) of FIG. 21 may be changed.

The MAC layer of the transmitting STA may request transmission of theMPDU to the PHY layer. A PSDU may correspond to an MPDU, and a header(that is, a PHY header) may be included in the front part of the PSDU. Atail bit and/or a padding bit may be included in the end part of thePSDU.

Scrambling and coding may be applied to PSDU. As a result, the PHYheader and PSDU of FIG. 21 may be converted into the SIG field and datafield of FIG. 20 .

FIG. 22 is a diagram illustrating an embodiment of the SIG 2030 field.

Referring to FIG. 22 , the SIG 2030 field may include 24-bitinformation. The RATE field of the SIG 2030 field may consist of 4 bitsand may include information on the RATE defined in the Mb/s unit. The Rfield of the SIG 2030 field may consist of 1 bit, may be a reservedfield, and may be used for various purposes. The length field of the SIG2030 field may include information about the number of octets of aphysical service data unit (PSDU) transmitted from the PHY layer. Aparity bit of the SIG 2030 field may be used for an even parity of 0 to16 bits of the SIG 2030 field. The Tail bits of the SIG 2030 field mayconsist of 6 bits and may be set to 0.

The MPDU may include at least one MSDU. In addition, the MPDU mayinclude a MAC header and a trailer. The structure of the MAC header maybe as follows.

FIG. 23 is a diagram illustrating an embodiment of a MAC header.

Referring to FIG. 23 , a MAC frame may include a MAC header, a framebody, and a frame check sequence (FCS). The MPDU may be definedaccording to various MAC frame formats. The MAC frame may be composed ofan MPDU, and may be transmitted/received through the PSDU of the datapart of the PPDU frame format.

The MAC header may include a frame control field, a duration/identifier(ID) field, an address field, and the like. The frame control field mayinclude control information necessary for frame transmission/reception.The duration/ID field may be set to a time for transmitting acorresponding frame or the like.

The duration/ID field included in the MAC header may be set to a lengthof 16 bits (for example, B0 to B15). Content included in the duration/IDfield may vary depending on a frame type and subtype, whether it istransmitted during a contention free period (CFP), QoS capability of atransmitting STA, and the like. In a control frame whose subtype isPS-Poll, the duration/ID field may include the AID of the transmittingSTA (for example, 14 LSB bits), and 2 MSB bits may be set to 1. Inframes transmitted during CFP by a point coordinator (PC) or non-QoSSTA, the duration/ID field may be set to a fixed value (for example,32768). In other frames transmitted by the non-QoS STA or control framestransmitted by the QoS STA, the duration/ID field may include a durationvalue defined for each frame type. In a data frame or a management frametransmitted by the QoS STA, the duration/ID field may include a durationvalue defined for each frame type. For example, if B15 of theduration/ID field is set to 0, it may indicate that the duration/IDfield is used to indicate the TXOP Duration, and B0 to B14 may be usedto indicate the actual TXOP Duration. The actual TXOP Duration indicatedby B0 to B14 may be any one of 0 to 32767, and the unit may bemicroseconds (us). When the duration/ID field indicates a fixed TXOPDuration value (for example, 32768), B15 may be 1, and B0 to B14 may beset to 0. Otherwise, when B14 is set to 1 and B15 is set to 1, theduration/ID field may be used to indicate an AID, and B0 to B13 mayindicate one AID from 1 to 2007.

The frame control field of the MAC header may include Protocol Version,Type, Subtype, To DS, From DS, More Fragment, Retry, Power Management,More Data, Protected Frame, and Order subfields.

FIG. 24 is a diagram illustrating an operation in each layer of awireless LAN system.

Referring to FIG. 24 , the transmitting STA and the receiving STA mayinclude a Layer 2 (that is, MAC layer) and a Layer 1 (that is, PHYlayer), and may generate MPDUs, PPDUs, and the like, as described inFIGS. 20 to 23 . That is, the transmitting STA may generate an MPDUincluding an MSDU and a MAC header. In addition, the transmitting STAmay generate a PPDU by adding a PHY preamble/header and the like to thePSDU corresponding to the generated MPDU.

The receiving STA may obtain the PSDU by removing the PHYpreamble/header and the like from the received PPDU, may obtain the MPDUcorresponding to the PSDU, may obtain the MSDU by removing the MACheader and the like from the MPDU, and may deliver the obtained MSDU toa higher layer.

As the wired/wireless traffic increases, the time latency-sensitivetraffic also increases. Time latency-sensitive traffic is usuallyreal-time audio/video transmission. With the proliferation of multimediadevices, the necessity of transmitting time latency-sensitive traffic inreal time in a wireless environment has increased. In a wirelessenvironment, there may be more considerations to supportlatency-sensitive traffic than in a wired environment. Transmission in awireless environment is slower than transmission in a wired environment,and there may be a lot of ambient interference.

In a wireless local area network (WLAN), there is no channel monopoly bya central base station. In a WLAN system, terminals must compete equallyin an industrial scientific medical (ISM) band. Therefore, it may bemore difficult to support traffic that is relatively sensitive to thetime delay in a WLAN system. Nevertheless, since time delay-sensitivetraffic is increasing, WLAN technology to support time delay-sensitivetraffic may be required. Techniques for supporting time delay-sensitivetraffic are described below.

The time delay may mean latency defined by the IEEE802.11ax task group.The time delay may mean the time from when a frame is received in thequeue of the medium access control (MAC) layer until the transmission inthe physical (PHY) layer is finished and an acknowledgment (ACK)/BlockACK is received from the receiving terminal, and the corresponding frameis deleted from the queue of the MAC layer.

Hereinafter, latency traffic may refer to traffic requiring low-latency,sensitive to time delay, or important in time delay.

Hereinafter, latency traffic may mean traffic having a new accesscategory different from the conventional one. For example, latencytraffic may mean traffic having a different quality of service (QoS)and/or traffic identifier (TID) from the related art. For example,traffic related to a specific AC (or QoS/TID) may be defined as latencytraffic, and the remaining ACs (or QoS/TID) may be defined as normaltraffic, not latency traffic. Alternatively, latency traffic and normaltraffic may have the same AC (or QoS/TID), and latency traffic andnormal traffic may be distinguished based on various proposedidentification fields (for example, bits of a PHY preamble and/or bitsof a MAC header). In IEEE 802.11ax, fields informing the buffer state ofthe terminal are defined in order to inform the AP of the buffer stateof the terminal. For example, the Queue Size subfield included in theQoS Control field is defined. For example, a buffer status report (BSR)control subfield is defined as one of the variants of the A-Controlsubfield included in the HT Control field. Upon receiving the Queue Sizesubfield and/or the BSR Control subfield, the AP may more efficientlyallocate uplink resources for uplink transmission of the UE. Forexample, the AP may receive information about the buffer state of theuser STA, and may configure a trigger frame for the user STA based onthe buffer state of the user STA. In the following example, an uplinkresource for uplink transmission may include an uplink resource used forUL MU communication. That is, in the following example, an uplink (UL)resource for uplink transmission may be a UL resource allocated throughFIGS. 11 to 13 and the like. The user STA may perform UL-MUcommunication as shown in FIG. 10 through the UL resource allocated bythe AP.

The Queue Size subfield may exist only in the Applicable type shown inTable 5 below, and may consist of 8 bits.

TABLE 5 Applicable frame Bits Bits Bits (sub) types 0-3 Bit 4 5-6 Bit 7Bits 8 Bit 9 Bit 10 11-15 QoS CF-Poll and QoS CF- TID EOSP Ack ReservedTXOP Limit Ack + CF-Poll frames sent Policy by HC QoS Data + CF-Poll andTID EOSP Ack A-MSDU TXOP Limit QoS Data + CF-Ack + CF- Policy PresentPoll frames sent by HC QoS Data and QoS Data + TID EOSP Ack A-MSDU AP PSBuffer State CF-Ack frames sent by Policy Present HC QoS Null framessent by TID EOSP Ack Reserved AP PS Buffer State HC Policy QoS Data andQoS Data + TID 0 Ack A-MSDU TXOP Duration Requested CF-Ack frames sentby Policy Present non-AP STAs that are not a TID 1 Ack A-MSDU Queue SizeTPU buffer STA or a TPU Policy Present sleep STA and a nonmesh BSS QoSNull frames sent by TID 0 Ack Reserved TXOP Duration Requested non-APSTAs that are not a Policy TPU buffer STA or a TPU TID 1 Ack ReservedQueue Size sleep STA in a nonmesh Policy BSS

The Queue Size subfield may inform the size of data currently stored inthe buffer among TID traffic related to the TID subfield. In IEEE802.11ax, the unit used in the Queue Size subfield may be determined as16, 256, 2048, or 32768 bytes according to the buffer size. For example,the Queue Size subfield is n-bit information (for example, 8-bitinformation), and may be used to report the size of uplink traffichaving a specific TID to the AP. The Queue Size subfield may be includedin the MAC header of the uplink PPDU of the user STA and delivered tothe AP. The AP may allocate uplink resources for the user STA based onthe Queue Size subfield. For example, the AP may use the reported QueueSize subfield when setting the length of the TXOP interval for UL-MUoperation or setting the frequency/spatial resource for the user STA.

FIG. 25 is a diagram illustrating an example of a BSR control subfield.

Referring to FIG. 25 , the BSR control subfield (or BSR subfield) mayinclude ACI Bitmap, Delta TID, ACI High, Scaling Factor, Queue SizeHigh, and Queue Size All fields. The Queue Size High and Queue Size Allfields may include information related to the size of uplink traffic ofthe user STA. Both the queue size subfield and the BSR control subfieldmay include information related to the size of uplink traffic of theuser STA. The Queue Size subfield and/or the BSR control subfield may beused for allocating uplink resources (for example,time/frequency/spatial resources for UL-MU communication) for the userSTA.

Hereinafter, subfields included in the BSR control subfield will bedescribed.

ACI Bitmap: Access category reported by UE

Delta TID: Providing TID information associated with ACI Bitmap subfieldvalues

ACI High: The access category in which the Queue Size is indicated bythe Queue Size High subfield

Scaling Factor: Information related to the unit to be used in the QueueSize High and Queue Size All subfields

Queue Size High: Queue size information for the access categoryindicated by the ACI High subfield

Queue Size All: Queue size information for the entire access categoriesindicated by the ACI Bitmap subfield

When the STA notifies the AP of information on the current uplinktraffic (that is, latency traffic) in order to transmit the latencytraffic, the AP may allocate a UL resource in consideration of thelatency of the uplink traffic (that is, latency traffic). Hereinafter, alatency BSR control subfield for latency traffic is described.

In order to transmit additional information for latency traffic,information related to latency traffic may be transmitted. That is,information related to traffic for which latency is important may betransmitted. A field including information related to latency trafficmay be called by various names, such as a latency BSR control subfield,a latency BSR subfield, and latency BSR information. Hereinafter, it maybe referred to as a latency BSR subfield.

The latency BSR subfield may include latency related information to bereported by the STA. For example, the latency BSR subfield may includeinformation related to latency-sensitive traffic (that is, latencytraffic) that the STA has. That is, the latency BSR subfield may includelatency BSR information. The latency BSR subfield may include some orall of the following information.

1. Time information

The latency BSR subfield may include information related to a time (orpacket arrival time) at which each packet enters a queue (for example, abuffer). The terminal (that is, the STA) and the AP may exchangeinformation related to the required latency of traffic. Accordingly,when the AP obtains information on the time at which the packet enteredthe buffer, the AP may calculate the remaining time for thecorresponding packet. That is, based on the time at which the packetentered the buffer, if a packet is not transmitted, the AP may acquireinformation related to the time remaining until the time when the packetis deleted from the buffer. That is, the AP may acquire informationrelated to the time remaining until the time when the packet is to betransmitted, based on the time at which the packet enters the buffer.That is, the AP may acquire information related to the time remaininguntil the delay bound of the corresponding packet based on the time atwhich the packet entered the buffer. The AP may allocate the UL resourceto the terminal (that is, the STA) based on information related to thequeue of each packet (for example, the arrival time (or packet arrivaltime) in the buffer) included in the BSR field.

The latency BSR subfield may include information related to the timeremaining until the delay bound of each packet. That is, since thelatency BSR subfield directly includes information related to the timeremaining until the delay bound of each packet, the AP can acquireinformation related to the time remaining until the delay bound of thecorresponding packet even if the AP does not calculate the timeremaining until the delay bound of the corresponding packet based on thepacket arrival time and the like. That is, the AP may acquireinformation related to the remaining time before the packet is droppedbased on the BSR field. That is, the terminal (STA) may transmitinformation related to the remaining time until the packet is dropped tothe AP. The AP may allocate the UL resource to the terminal (that is,the STA) based on information related to the time remaining until theDelay bound of each packet included in the BSR field.

2. Size information

The latency BSR subfield may include information related to the numberof buffered packets stored in the buffer.

The latency BSR subfield may include information related to the lengthof buffered packets stored in the buffer.

The AP may determine the size of a resource to be allocated to theterminal based on information related to the number of packets stored inthe buffer and the size of each packet stored in the buffer included inthe latency BSR subfield.

FIG. 26 illustrates an example of a latency BSR subfield.

Referring to FIG. 26 , the latency BSR subfield may include, forexample, time information and size information one by one. Specific bitsof the latency BSR subfield may vary according to implementation.

FIG. 26 is only an example, and the latency BSR subfield may includeboth the time information and the size information described above, ormay include only a part of the time information and the size informationdescribed above. For example, the latency BSR subfield may includeinformation on a packet arrival time, the number of packets stored inthe buffer, and the size of each packet stored in the buffer.

Some of the latency BSR information may also be used to transmitinformation on traffic that is not latency traffic (that is, trafficsensitive to time delay). For example, packet arrival time informationfor traffic in which latency is not important may also be included inthe latency BSR subfield. For example, the AP may allocate a UL resourceto the terminal based on packet arrival time information for traffic forwhich latency is not important. Accordingly, the terminal may transmittraffic information including packet arrival time information of trafficfor which latency is not important to the AP.

Hereinafter, a method for transmitting latency BSR information isdescribed.

1. The QoS control field may include a Queue Size subfield. In addition,the latency BSR subfield may be defined using a variant of the A-Controlsubfield included in the HT Control field. For example, the PPDU mayinclude a Queue Size subfield, a BSR Control subfield, and a Latency BSRsubfield. For example, the Queue Size subfield (and/or the BSR controlsubfield) and the Latency BSR subfield may be included in the MAC headerof the same PPDU. For example, the queue size subfield (and/or the BSRcontrol subfield) and the latency BSR subfield may be included in MACheaders of different PPDUs, and the different PPDUs may be transmittedin the same TXOP.

The Queue Size subfield may include information related to a queue sizeof latency traffic, or information related to a queue size of trafficother than latency traffic or all traffic. Specifically, 1) for example,the Queue size subfield and/or the BSR control subfield may be used fornormal traffic queue size information other than latency traffic, andthe latency BSR subfield may be used for traffic queue size informationof latency traffic. 2) For example, the Queue Size subfield and/or BSRcontrol subfield may be used for queue size information for both latencytraffic and normal traffic, and the latency BSR subfield may be used fortraffic queue size information of latency traffic. That is, in both 1)and 2), the latency BSR subfield may include only information related tothe queue size of latency traffic. However, in 1), the Queue sizesubfield and/or the BSR control subfield may include only normal trafficqueue size information, in 2), the queue size subfield and/or the BSRcontrol subfield may include both normal traffic queue size informationand latency traffic queue size information. It is not limited to theabove embodiment, and various examples of queue size information may betransmitted.

2. For example, the latency BSR subfield may be transmittedindependently. The latency BSR subfield may be included in another frameand transmitted or may be transmitted in another TXOP separately fromthe Queue Size subfield and/or the BSR control subfield. For example,the Queue Size subfield (and/or the BSR control subfield) and theLatency BSR subfield may be included in different PPDUs (that is, in MACheaders of different PPDUs). For example, the Queue Size subfield(and/or the BSR control subfield) and the latency BSR subfield may betransmitted through different TXOP intervals.

3. For example, some subfields of the existing BSR (that is, QoSsubfield and/or BSR control subfield) and the latency BSR subfield maybe integrated. For example, latency BSR information may be includedinstead of some fields of the existing BSR (that is, QoS subfield and/orBSR control subfield).

For example, since the ACI High and Queue Size High subfields of the BSRcontrol subfield inform the queue size information of a specific AC,this information is omitted and replaced with Latency BSR information.That is, the ACI High and Queue Size High subfields of the BSR controlsubfield may include latency BSR information. This is because queue sizeinformation of a specific AC can be informed by the QoS Control field.For example, the Queue Size subfield (and/or the BSR control subfield)and the Latency BSR subfield may consist of one field. For example, theACI High and Queue Size High subfields of FIG. 25 may be omitted andLatency BSR information may be included instead. For example, in orderto transmit only latency-related information, the Queue Size Allsubfield of FIG. 25 , which is information on the entire queue size, maybe omitted, and latency BSR information may be included instead.Alternatively, the latency BSR field may be included instead of othersubfields of the BSR control subfield.

For example, latency information (for example, latency BSR information)may be transmitted through the HLA control field. Hereinafter, a methodin which the latency information is transmitted through the HLA controlfield will be described.

FIG. 27 is a diagram illustrating an HE link adaptation (HLA) controlfield.

FIG. 27 may be an HLA control field defined in IEEE802.11ax. Referringto FIG. 27 , the definition of each subfield included in the HLA controlfield may be as follows.

Unsolicited MFB: The Unsolicited MFB subfield indicates whethercurrently transmitted feedback information is transmitted in a solicitmanner or an unsolicited manner For example, the Unsolicited MFBsubfield may include information related to whether the STA transmitsfeedback information that is requested or feedback information that isnot requested.

MRQ: The MRQ subfield is used to distinguish feedback information whenrequesting or responding to it. For example, the MRQ subfield mayinclude information related to whether the STA is requesting feedbackinformation or responding to the requested feedback.

NSS: Recommended number of spatial streams. For example, the NSSsubfield may include information related to the number of spatialstreams recommended by the STA. That is, the NSS subfield may includeinformation related to an appropriate number of spatial streams which isdetermined by the STA.

HE-MCS: Recommended MCS. For example, the HE-MCS subfield may includeinformation related to a modulation and coding scheme (MCS) recommendedby the STA. That is, the HE-MCS subfield may include information relatedto an appropriate MCS which is determined by the STA.

DCM: Recommended usage of dual carrier modulation. For example, the dualcarrier modulation (DCM) subfield may include information related towhether the STA recommends using DCM. That is, the DCM subfield mayinclude information related to whether the use of DCM is appropriate,which is determined by the STA.

RU Allocation: Recommended RU. For example, the RU Allocation subfieldmay include RU allocation information recommended by the STA. Forexample, the RU Allocation subfield may include information related tothe RU size recommended by the STA.

BW: Recommended Bandwidth. For example, the BW subfield may includebandwidth information recommended by the STA. For example, the BWsubfield may include information related to an appropriate bandwidthwhich is determined by the STA.

MSI/Partial PPDU Parameters: In case of unsolicited feedback, theMSI/Partial PPDU Parameters subfield may include information on PPDUformat and coding type, in the case of solicited feedback or feedbackrequest, it may include sequence information of the PPDU which is to bemeasured/which was already measured.

Tx Beamforming: The Tx Beamforming subfield informs whether beamformingof a PPDU for measurement is performed. For example, the Tx Beamformingsubfield may include information related to a transmission type of ameasured PPDU.

UL HE TB PPDU MFB: It indicates that the information recommended aboveis for UL HE TB PPDU transmission.

A method for transmitting latency information using a subfield of theHLA control field is as follows.

A reserved bit of the HLA control field may indicate information relatedto whether the corresponding HLA control field includes latencyinformation. If the HLA control field includes latency information, forexample, the DCM (1 bit), MSI/Partial PPDU Parameters (3 bits), and TxBeamforming (1 bit) subfields of the HLA control field may includelatency information unlike those defined in IEEE802.11ax. For example,only a part of DCM (1 bit), MSI/Partial PPDU Parameters (3 bits), and TxBeamforming (1 bit) subfields may include latency information, andanother subfield included in the HLA control field may also includelatency information.

The latency information included in the HLA control field may includethe aforementioned latency BSR information (for example, packet arrivaltime (information related to the time when low-latency traffic is storedin a buffer, etc.) and the following information.

Recommended duration of UL HE TB PPDU: When the STA is transmittinglatency traffic using an uplink trigger based (UL TB) PPDU, the intervalbetween each UL TB PPDU, that is, the duration of a trigger frame mayhave a significant effect on latency performance Accordingly, the STAmay request the period of the UL TB PPDU to the AP. For example, the STAmay transmit information related to the recommended duration of the ULHE TB PPDU. For example, the STA may transmit information related to atime interval of an uplink trigger based PPDU (UL TB PPDU).

Recommended length of UL HE TB PPDU: When the STA is transmittinglatency traffic using the UL TB PPDU, the length of the UL TB PPDU mayaffect latency performance If the length of the UL TB PPDU is too short,it may be insufficient to sufficiently transmit latency traffic. If thelength of the UL TB PPDU is too long, the transmission time increasesdue to unnecessary padding, which may increase the time delay.Accordingly, the STA could recommend an appropriate length of the UL TBPPDU to the AP. For example, the STA may transmit information related tothe length of the UL TB PPDU. The AP may determine the appropriatelength of the TB PPDU based on the recommended length of UL HE TB PPDUreceived from the STA.

FIG. 28 is a flowchart for explaining an embodiment of a STA operation.

Referring to FIG. 28 , a STA may be associated with an AP (S2810). Forexample, the STA may transmit capability information on whether tosupport low-latency traffic to the AP. That is, the STA may transmitinformation on whether it supports low-latency traffic through a beacon,a probe request, a probe response, an association request, anassociation response, other management frames, other control frames, andthe like. Transmission of capability information may be performed in theassociation step or may be performed in a separate step.

For example, the STA may transmit capability information on whether tosupport Latency BSR to the AP. Latency BSR may refer to an operation ofreporting “latency BSR information” to the AP according to theabove-described example. For example, latency information (for example,latency BSR information) may be transmitted through the HLA controlfield. The STA may transmit information on whether it supports theLatency BSR through a beacon, a probe request, a probe response, anassociation request, an association response, other management frames,other control frames, and the like. Transmission of capabilityinformation may be performed in an association step or may be performedin a separate step.

The STA may transmit a link adaptation control field (for example, anHLA control field) (S2820). For example, the STA may transmit a firstphysical protocol data unit (PPDU) including a link adaptation controlfield. The link adaptation control field may include a bit indicatingwhether the link adaptation control field includes information relatedto low-latency traffic. The low-latency traffic may be traffic requiringa delay less than or equal to a threshold value.

For example, the structure of the link adaptation control field may beconfigured based on FIG. 27 . For example, the link adaptation controlfield may include the following subfields.

Unsolicited MFB: The Unsolicited MFB subfield indicates whethercurrently transmitted feedback information is transmitted in a solicitmanner or an unsolicited manner For example, the Unsolicited MFBsubfield may include information related to whether the STA transmitsfeedback information that is requested or feedback information that isnot requested.

MRQ: The MRQ subfield is used to distinguish feedback information whenrequesting or responding to it. For example, the MRQ subfield mayinclude information related to whether the STA is requesting feedbackinformation or responding to the requested feedback.

NSS: Recommended number of spatial streams. For example, the NSSsubfield may include information related to the number of spatialstreams recommended by the STA. That is, the NSS subfield may includeinformation related to an appropriate number of spatial streams which isdetermined by the STA.

HE-MCS: Recommended MCS. For example, the HE-MCS subfield may includeinformation related to a modulation and coding scheme (MCS) recommendedby the STA. That is, the HE-MCS subfield may include information relatedto an appropriate MCS which is determined by the STA.

DCM: Recommended usage of dual carrier modulation. For example, the dualcarrier modulation (DCM) subfield may include information related towhether the STA recommends using DCM. That is, the DCM subfield mayinclude information related to whether the use of DCM is appropriate,which is determined by the STA.

RU Allocation: Recommended RU. For example, the RU Allocation subfieldmay include RU allocation information recommended by the STA. Forexample, the RU Allocation subfield may include information related tothe RU size recommended by the STA.

BW: Recommended Bandwidth. For example, the BW subfield may includebandwidth information recommended by the STA. For example, the BWsubfield may include information related to an appropriate bandwidthwhich is determined by the STA.

MSI/Partial PPDU Parameters: In case of unsolicited feedback, theMSI/Partial PPDU Parameters subfield may include information on PPDUformat and coding type, in the case of solicited feedback or feedbackrequest, it may include sequence information of the PPDU which is to bemeasured/which was already measured.

Tx Beamforming: The Tx Beamforming subfield informs whether beamformingof a PPDU for measurement is performed. For example, the Tx Beamformingsubfield may include information related to a transmission type of ameasured PPDU.

UL HE TB PPDU MFB: It indicates that the information recommended aboveis for UL HE TB PPDU transmission.

A method for transmitting latency information using a subfield of theHLA control field is as follows.

A reserved bit of the HLA control field may indicate information relatedto whether the corresponding HLA control field includes latencyinformation. If the HLA control field includes latency information, forexample, the DCM (1 bit), MSI/Partial PPDU Parameters (3 bits), and TxBeamforming (1 bit) subfields of the HLA control field may includelatency information unlike those defined in IEEE802.11ax. For example,only a part of DCM (1 bit), MSI/Partial PPDU Parameters (3 bits), and TxBeamforming (1 bit) subfields may include latency information, andanother subfield included in the HLA control field may also includelatency information.

The latency information included in the HLA control field may includethe aforementioned latency BSR information (for example, packet arrivaltime (information related to the time when low-latency traffic is storedin a buffer, etc.) and the following information.

Recommended duration of UL HE TB PPDU: When the STA is transmittinglatency traffic using an uplink trigger based (UL TB) PPDU, the intervalbetween each UL TB PPDU, that is, the duration of a trigger frame mayhave a significant effect on latency performance Accordingly, the STAmay request the period of the UL TB PPDU to the AP. For example, the STAmay transmit information related to the recommended duration of the ULHE TB PPDU. For example, the STA may transmit information related to atime interval of an uplink trigger based PPDU (UL TB PPDU).

Recommended length of UL HE TB PPDU: When the STA is transmittinglatency traffic using the UL TB PPDU, the length of the UL TB PPDU mayaffect latency performance If the length of the UL TB PPDU is too short,it may be insufficient to sufficiently transmit latency traffic. If thelength of the UL TB PPDU is too long, the transmission time increasesdue to unnecessary padding, which may increase the time delay.Accordingly, the STA could recommend an appropriate length of the UL TBPPDU to the AP. For example, the STA may transmit information related tothe length of the UL TB PPDU. The AP may determine the appropriatelength of the TB PPDU based on the recommended length of UL HE TB PPDUreceived from the STA.

For example, the link adaptation control field may include firstinformation or second information based on a bit indicating whether ornot to include information related to the low-latency traffic. The firstinformation may include at least one of whether dual carrier modulation(DCM) is used, a PPDU format, a coding type, a PPDU sequence, andwhether or not beamforming is used. The second information may includeat least one of information related to the time when the low-latencytraffic is stored in the buffer, information related to the timeinterval of an uplink trigger based PPDU (UL TB PPDU), and informationrelated to the length of the UL TB PPDU.

For example, the link adaptation control field may be transmittedindependently.

The link adaptation control field may include latency relatedinformation to be reported by the STA. For example, the link adaptationcontrol field may include information related to latency-sensitivetraffic (that is, latency-traffic) that the STA has. That is, the linkadaptation control field may include latency information (for example,latency BSR information). The link adaptation control field may includesome or all of the information below.

1. Time information

The link adaptation control field may include information related to atime (or packet arrival time) at which each packet enters a queue (forexample, a buffer). The terminal (that is, the STA) and the AP mayexchange information related to the required latency of traffic.Accordingly, when the AP obtains information on the time at which thepacket entered the buffer, the AP may calculate the remaining time forthe corresponding packet. That is, based on the time at which the packetentered the buffer, if a packet is not transmitted, the AP may acquireinformation related to the time remaining until the time when the packetis deleted from the buffer. That is, the AP may acquire informationrelated to the time remaining until the time when the packet is to betransmitted, based on the time at which the packet enters the buffer.That is, the AP may acquire information related to the time remaininguntil the delay bound of the corresponding packet based on the time atwhich the packet entered the buffer. The AP may allocate the UL resourceto the terminal (that is, the STA) based on information related to thequeue of each packet (for example, the arrival time (or packet arrivaltime) in the buffer) included in the BSR field. Accordingly, the AP canobtain the effect of allocating sufficient resources so that the STAhaving low-latency traffic can perform fast transmission.

The link adaptation control field may include information related to thetime remaining until the delay bound of each packet. That is, since thelatency BSR subfield directly includes information related to the timeremaining until the delay bound of each packet, the AP can acquireinformation related to the time remaining until the delay bound of thecorresponding packet even if the AP does not calculate the timeremaining until the delay bound of the corresponding packet based on thepacket arrival time and the like. That is, the AP may acquireinformation related to the remaining time before the packet is droppedbased on the BSR field. That is, the terminal (STA) may transmitinformation related to the remaining time until the packet is dropped tothe AP. The AP may allocate the UL resource to the terminal (that is,the STA) based on information related to the time remaining until theDelay bound of each packet included in the BSR field. Accordingly, theAP can obtain the effect of allocating sufficient resources so that theSTA having low-latency traffic can perform fast transmission.

2. Size information

The link adaptation control field may include information related to thenumber of buffered packets stored in the buffer.

The link adaptation control field may include information related to thelength of buffered packets stored in the buffer.

The AP may determine the size of a resource to be allocated to theterminal based on information related to the number of packets stored inthe buffer and the size of each packet stored in the buffer included inthe link adaptive control field. That is, the AP can obtain the effectof being able to determine the amount of resources required to satisfythe latency of the STA having traffic requiring low-latency.

Since the STA can separately transmit latency information (for example,latency BSR information) for latency traffic, the AP can obtain theeffect of efficiently performing resource allocation for latencytraffic, accordingly, the STA can also obtain the effect of transmittingthe latency-traffic to satisfy the required latency.

The STA may be allocated a resource for low-latency traffic (S2830). Forexample, the STA may be allocated a resource for low-latency traffic(that is, latency traffic) from the AP. Upon receiving the linkadaptation control field, the AP may more efficiently allocate uplinkresources for uplink transmission of the STA. For example, the AP mayreceive information about the buffer state of the STA, and may configurea trigger frame for the user STA based on the buffer state of the STA.The uplink resource for uplink transmission may include an uplinkresource used for UL MU communication. That is, an uplink (UL) resourcefor uplink transmission may be a UL resource allocated through FIGS. 11to 13 and the like. The user STA may perform UL-MU communication asshown in FIG. 10 through the UL resource allocated by the AP. That is,the AP may allocate a resource to the STA based on the information (thatis, link adaptation control field) related to the low-latency trafficreceived in step S2820.

The STA may transmit low-latency traffic through the resource allocatedfrom the AP (S2840). For example, the STA may transmit a second PPDUincluding low-latency traffic through the resource allocated from theAP. For example, the low-latency traffic may be traffic requiring adelay less than or equal to a threshold value.

The STA may configure a PPDU including low-latency traffic and transmitit to the AP. A specific method for configuring the PPDU may be based onat least one of the examples of FIGS. 20 to 24 . For example, the STAmay configure a data field (that is, PSDU) based on a MAC PDU includinglow-latency traffic and a MAC header for the MAC PDU. For example, theMAC header may include information about the type of the traffic (thatis, low-latency type) included in the data field. In addition, the STAmay configure the EHT-PPDU by attaching the above-described PHYpreamble/signal (for example, L-STF, L-LTF, L-SIG, EHT-SIG, EHT-STF,EHT-LTF) to the data field. For example, the PHY preamble/signal mayinclude information about the type of traffic (that is, low-latencytype).

The STA may transmit a link adaptation control field (S2850). Forexample, the STA may transmit a third physical protocol data unit (PPDU)including a link adaptation control field (for example, the linkadaptation control field may include information related to low-latencytraffic). For example, the low-latency traffic may be traffic requiringa delay less than or equal to a threshold value. Information related tolow-latency traffic may be transmitted at any time. For example, the STAmay periodically transmit a link adaptation control field (that is, alink adaptation control field including information related tolow-latency traffic) to the AP. For example, the STA may aperiodicallytransmit information related to low-latency traffic to the AP. Forexample, the STA may transmit information related to low-latency trafficto the AP whenever low-latency traffic occurs or there is a change inthe low-latency traffic stored in the queue.

For example, the first PPDU and the second PPDU may be transmitted inthe different transmission opportunities (TXOPs). For example, thelow-latency traffic may have an access category for the low-latencytraffic.

FIG. 29 is a flowchart for explaining an embodiment of an AP operation.

Referring to FIG. 29 , the AP may be associated with the STA (S2910).For example, the STA may transmit capability information on whether tosupport low-latency traffic to the AP. That is, the STA may transmitinformation on whether it supports low-latency traffic through a beacon,a probe request, a probe response, an association request, anassociation response, other management frames, other control frames, andthe like. Transmission of capability information may be performed in theassociation step or may be performed in a separate step.

For example, the STA may transmit capability information on whether tosupport Latency BSR to the AP. Latency BSR may refer to an operation ofreporting “latency BSR information” to the AP according to theabove-described example. For example, latency information (for example,latency BSR information) may be transmitted through the HLA controlfield. The STA may transmit information on whether it supports theLatency BSR through a beacon, a probe request, a probe response, anassociation request, an association response, other management frames,other control frames, and the like. Transmission of capabilityinformation may be performed in an association step or may be performedin a separate step.

The AP may receive a link adaptation control field (for example, an HLAcontrol field) (S2920). For example, the AP may receive a first physicalprotocol data unit (PPDU) including a link adaptation control field.Link adaptation control field may include a bit indicating whether thelink adaptation control field includes information related tolow-latency traffic. The low-latency traffic may be traffic requiring alatency less than or equal to a threshold value.

For example, the structure of the link adaptation control field may beconfigured based on FIG. 27 . For example, the link adaptation controlfield may include the following subfields.

Unsolicited MFB: The Unsolicited MFB subfield indicates whethercurrently transmitted feedback information is transmitted in a solicitmanner or an unsolicited manner For example, the Unsolicited MFBsubfield may include information related to whether the STA transmitsfeedback information that is requested or feedback information that isnot requested.

MRQ: The MRQ subfield is used to distinguish feedback information whenrequesting or responding to it. For example, the MRQ subfield mayinclude information related to whether the STA is requesting feedbackinformation or responding to the requested feedback.

NSS: Recommended number of spatial streams. For example, the NSSsubfield may include information related to the number of spatialstreams recommended by the STA. That is, the NSS subfield may includeinformation related to an appropriate number of spatial streams which isdetermined by the STA.

HE-MCS: Recommended MCS. For example, the HE-MCS subfield may includeinformation related to a modulation and coding scheme (MCS) recommendedby the STA. That is, the HE-MCS subfield may include information relatedto an appropriate MCS which is determined by the STA.

DCM: Recommended usage of dual carrier modulation. For example, the dualcarrier modulation (DCM) subfield may include information related towhether the STA recommends using DCM. That is, the DCM subfield mayinclude information related to whether the use of DCM is appropriate,which is determined by the STA.

RU Allocation: Recommended RU. For example, the RU Allocation subfieldmay include RU allocation information recommended by the STA. Forexample, the RU Allocation subfield may include information related tothe RU size recommended by the STA.

BW: Recommended Bandwidth. For example, the BW subfield may includebandwidth information recommended by the STA. For example, the BWsubfield may include information related to an appropriate bandwidthwhich is determined by the STA.

MSI/Partial PPDU Parameters: In case of unsolicited feedback, theMSI/Partial PPDU Parameters subfield may include information on PPDUformat and coding type, in the case of solicited feedback or feedbackrequest, it may include sequence information of the PPDU which is to bemeasured/which was already measured.

Tx Beamforming: The Tx Beamforming subfield informs whether beamformingof a PPDU for measurement is performed. For example, the Tx Beamformingsubfield may include information related to a transmission type of ameasured PPDU.

UL HE TB PPDU MFB: It indicates that the information recommended aboveis for UL HE TB PPDU transmission.

A method for transmitting latency information using a subfield of theHLA control field is as follows.

A reserved bit of the HLA control field may indicate information relatedto whether the corresponding HLA control field includes latencyinformation. If the HLA control field includes latency information, forexample, the DCM (1 bit), MSI/Partial PPDU Parameters (3 bits), and TxBeamforming (1 bit) subfields of the HLA control field may includelatency information unlike those defined in IEEE802.11ax. For example,only a part of DCM (1 bit), MSI/Partial PPDU Parameters (3 bits), and TxBeamforming (1 bit) subfields may include latency information, andanother subfield included in the HLA control field may also includelatency information.

The latency information included in the HLA control field may includethe aforementioned latency BSR information (for example, packet arrivaltime (information related to the time when low-latency traffic is storedin a buffer, etc.) and the following information.

Recommended duration of UL HE TB PPDU: When the STA is transmittinglatency traffic using an uplink trigger based (UL TB) PPDU, the intervalbetween each UL TB PPDU, that is, the duration of a trigger frame mayhave a significant effect on latency performance Accordingly, the STAmay request the period of the UL TB PPDU to the AP. For example, the STAmay transmit information related to the recommended duration of the ULHE TB PPDU. For example, the STA may transmit information related to atime interval of an uplink trigger based PPDU (UL TB PPDU).

Recommended length of UL HE TB PPDU: When the STA is transmittinglatency traffic using the UL TB PPDU, the length of the UL TB PPDU mayaffect latency performance If the length of the UL TB PPDU is too short,it may be insufficient to sufficiently transmit latency traffic. If thelength of the UL TB PPDU is too long, the transmission time increasesdue to unnecessary padding, which may increase the time delay.Accordingly, the STA could recommend an appropriate length of the UL TBPPDU to the AP. For example, the STA may transmit information related tothe length of the UL TB PPDU. The AP may determine the appropriatelength of the TB PPDU based on the recommended length of UL HE TB PPDUreceived from the STA.

For example, the link adaptation control field may include firstinformation or second information based on a bit indicating whether ornot to include information related to the low-latency traffic. The firstinformation may include at least one of whether dual carrier modulation(DCM) is used, a PPDU format, a coding type, a PPDU sequence, andwhether or not beamforming is used. The second information may includeat least one of information related to the time when the low-latencytraffic is stored in the buffer, information related to the timeinterval of an uplink trigger based PPDU (UL TB PPDU), and informationrelated to the length of the UL TB PPDU.

For example, the link adaptation control field may be transmittedindependently.

The link adaptation control field may include latency relatedinformation to be reported by the STA. For example, the link adaptationcontrol field may include information related to latency-sensitivetraffic (that is, latency-traffic) that the STA has. That is, the linkadaptation control field may include latency information (for example,latency BSR information). The link adaptation control field may includesome or all of the information below.

1. Time information

The link adaptation control field may include information related to atime (or packet arrival time) at which each packet enters a queue (forexample, a buffer). The terminal (that is, the STA) and the AP mayexchange information related to the required latency of traffic.Accordingly, when the AP obtains information on the time at which thepacket entered the buffer, the AP may calculate the remaining time forthe corresponding packet. That is, based on the time at which the packetentered the buffer, if a packet is not transmitted, the AP may acquireinformation related to the time remaining until the time when the packetis deleted from the buffer. That is, the AP may acquire informationrelated to the time remaining until the time when the packet is to betransmitted, based on the time at which the packet enters the buffer.That is, the AP may acquire information related to the time remaininguntil the delay bound of the corresponding packet based on the time atwhich the packet entered the buffer. The AP may allocate the UL resourceto the terminal (that is, the STA) based on information related to thequeue of each packet (for example, the arrival time (or packet arrivaltime) in the buffer) included in the BSR field. Accordingly, the AP canobtain the effect of allocating sufficient resources so that the STAhaving low-latency traffic can perform fast transmission.

The link adaptation control field may include information related to thetime remaining until the delay bound of each packet. That is, since thelatency BSR subfield directly includes information related to the timeremaining until the delay bound of each packet, the AP can acquireinformation related to the time remaining until the delay bound of thecorresponding packet even if the AP does not calculate the timeremaining until the delay bound of the corresponding packet based on thepacket arrival time and the like. That is, the AP may acquireinformation related to the remaining time before the packet is droppedbased on the BSR field. That is, the terminal (STA) may transmitinformation related to the remaining time until the packet is dropped tothe AP. The AP may allocate the UL resource to the terminal (that is,the STA) based on information related to the time remaining until theDelay bound of each packet included in the BSR field. Accordingly, theAP can obtain the effect of allocating sufficient resources so that theSTA having low-latency traffic can perform fast transmission.

2. Size information

The link adaptation control field may include information related to thenumber of buffered packets stored in the buffer.

The link adaptation control field may include information related to thelength of buffered packets stored in the buffer.

The AP may determine the size of a resource to be allocated to theterminal based on information related to the number of packets stored inthe buffer and the size of each packet stored in the buffer included inthe link adaptive control field. That is, the AP can obtain the effectof being able to determine the amount of resources required to satisfythe latency of the STA having traffic requiring low-latency.

Since the STA can separately transmit latency information (for example,latency BSR information) for latency traffic, the AP can obtain theeffect of efficiently performing resource allocation for latencytraffic, accordingly, the STA can also obtain the effect of transmittingthe latency-traffic to satisfy the required latency. Since the STA cantransmit latency information for latency traffic by including it in thelink adaptation control field,

AP may allocate resources for low-latency traffic (S2930). For example,the AP may allocate a resource for low-latency traffic (that is, latencytraffic) to the STA. Upon receiving the link adaptation control field,the AP may more efficiently allocate uplink resources for uplinktransmission of the STA. For example, the AP may receive informationabout the buffer state of the STA, and may configure a trigger frame forthe user STA based on the buffer state of the STA. The uplink resourcefor uplink transmission may include an uplink resource used for UL MUcommunication. That is, an uplink (UL) resource for uplink transmissionmay be a UL resource allocated through FIGS. 11 to 13 and the like. Theuser STA may perform UL-MU communication as shown in FIG. 10 through theUL resource allocated by the AP. That is, the AP may allocate resourcesto the STA based on the information (that is, link adaptation controlfield) related to the low-latency traffic received in step S2820.

The AP may receive low-latency traffic through the resource allocated tothe STA (S2940). For example, the AP may receive the second PPDUincluding low-latency traffic through the resource allocated to the STA.For example, the low-latency traffic may be traffic requiring a latencyless than or equal to a threshold value.

The STA may configure a PPDU including low-latency traffic and transmitit to the AP. A specific method for configuring the PPDU may be based onat least one of the examples of FIGS. 20 to 24 . For example, the STAmay configure a data field (that is, PSDU) based on a MAC PDU includinglow-latency traffic and a MAC header for the MAC PDU. For example, theMAC header may include information about the type of the traffic (thatis, low-latency type) included in the data field. In addition, the STAmay configure the EHT-PPDU by attaching the above-described PHYpreamble/signal (for example, L-STF, L-LTF, L-SIG, EHT-SIG, EHT-STF,EHT-LTF) to the data field. For example, the PHY preamble/signal mayinclude information about the type of traffic (that is, low-latencytype).

The AP may receive a link adaptation control field (S2950). For example,the AP may transmit a third physical protocol data unit (PPDU) includinga link adaptation control field (for example, the link adaptationcontrol field may include information related to low-latency traffic).For example, the low-latency traffic may be traffic requiring a delayless than or equal to a threshold value. Information related tolow-latency traffic may be transmitted at any time. For example, the APmay periodically receive a link adaptation control field (that is, alink adaptation control field including information related tolow-latency traffic) from the STA. For example, the AP may aperiodicallyreceive information related to low-latency traffic from the STA. Forexample, the STA may transmit information related to low-latency trafficto the AP whenever low-latency traffic occurs or there is a change inthe low-latency traffic stored in the queue.

For example, the first PPDU and the second PPDU may be transmitted inthe different transmission opportunities (TXOPs). For example, thelow-latency traffic may have an access category for the low-latencytraffic.

Some of the detailed steps shown in the examples of FIGS. 28 and 29 maybe omitted, and other steps may be added. For example, the step ofperforming association with the AP (S2810) of FIG. 28 , the step oftransmitting information related to low-latency traffic (S2850) may beomitted. The order of the steps shown in FIGS. 28 and 29 may vary.

The technical features of the present disclosure described above may beapplied to various devices and methods. For example, the above-describedtechnical features of the present disclosure may be performed/supportedthrough the apparatus of FIGS. 1 and/or 19 . For example, theabove-described technical features of the present disclosure may beapplied only to a part of FIGS. 1 and/or 19 . For example, the technicalfeatures of the present disclosure described above may be implementedbased on the processing chips 114 and 124 of FIG. 1 , may be implementedbased on the processors 111 and 121 and the memories 112 and 122 of FIG.1 , or may be implemented based on the processor 610 and the memory 620of FIG. 19 . For example, the apparatus of the present disclosureincludes a memory and a processor operatively coupled to the memory. Theprocessor may be configured to transmit a first physical protocol dataunit (PPDU) including a link adaptation control field. The linkadaptation control field may include a bit indicating whether the linkadaptation control field includes information related to low-latencytraffic. The low-latency traffic may be traffic requiring a latency lessthan or equal to a threshold value. The processor may be configured toreceive an allocation of a resource for the low-latency traffic. Theprocessor may be configured to transmit the second PPDU including thelow-latency traffic through the resource.

The technical features of the present disclosure may be implementedbased on a computer readable medium (CRM). For example, a CRM proposedby the present disclosure may store instructions which, based on beingexecuted by at least one processor of a station (STA) in a wirelesslocal area network system, cause the STA to perform operations. Theoperations may include the step of transmitting a first physicalprotocol data unit (PPDU) including a link adaptation control field. Thelink adaptation control field may include a bit indicating whether thelink adaptation control field includes information related tolow-latency traffic. The low-latency traffic may be traffic requiring alatency less than or equal to a threshold value. The operations mayinclude the step of receiving an allocation of a resource for thelow-latency traffic. The operations may include the step of transmittingthe second PPDU including the low-latency traffic through the resource.The instructions stored in the CRM of the present disclosure may beexecuted by at least one processor. At least one processor related toCRM in the present disclosure may be the processors 111 and 121 or theprocessing chips 114 and 124 of FIG. 1 , or the processor 610 of FIG. 19. Meanwhile, the CRM of the present disclosure may be the memories 112and 122 of FIG. 1 , the memory 620 of FIG. 19 , or a separate externalmemory/storage medium/disk.

The foregoing technical features of the present specification areapplicable to various applications or business models. For example, theforegoing technical features may be applied for wireless communicationof a device supporting artificial intelligence (AI).

Artificial intelligence refers to a field of study on artificialintelligence or methodologies for creating artificial intelligence, andmachine learning refers to a field of study on methodologies fordefining and solving various issues in the area of artificialintelligence. Machine learning is also defined as an algorithm forimproving the performance of an operation through steady experiences ofthe operation.

An artificial neural network (ANN) is a model used in machine learningand may refer to an overall problem-solving model that includesartificial neurons (nodes) forming a network by combining synapses. Theartificial neural network may be defined by a pattern of connectionbetween neurons of different layers, a learning process of updating amodel parameter, and an activation function generating an output value.

The artificial neural network may include an input layer, an outputlayer, and optionally one or more hidden layers. Each layer includes oneor more neurons, and the artificial neural network may include synapsesthat connect neurons. In the artificial neural network, each neuron mayoutput a function value of an activation function of input signals inputthrough a synapse, weights, and deviations.

A model parameter refers to a parameter determined through learning andincludes a weight of synapse connection and a deviation of a neuron. Ahyper-parameter refers to a parameter to be set before learning in amachine learning algorithm and includes a learning rate, the number ofiterations, a mini-batch size, and an initialization function.

Learning an artificial neural network may be intended to determine amodel parameter for minimizing a loss function. The loss function may beused as an index for determining an optimal model parameter in a processof learning the artificial neural network.

Machine learning may be classified into supervised learning,unsupervised learning, and reinforcement learning.

Supervised learning refers to a method of training an artificial neuralnetwork with a label given for training data, wherein the label mayindicate a correct answer (or result value) that the artificial neuralnetwork needs to infer when the training data is input to the artificialneural network. Unsupervised learning may refer to a method of trainingan artificial neural network without a label given for training data.Reinforcement learning may refer to a training method for training anagent defined in an environment to choose an action or a sequence ofactions to maximize a cumulative reward in each state.

Machine learning implemented with a deep neural network (DNN) includinga plurality of hidden layers among artificial neural networks isreferred to as deep learning, and deep learning is part of machinelearning. Hereinafter, machine learning is construed as including deeplearning.

The foregoing technical features may be applied to wirelesscommunication of a robot.

Robots may refer to machinery that automatically process or operate agiven task with own ability thereof. In particular, a robot having afunction of recognizing an environment and autonomously making ajudgment to perform an operation may be referred to as an intelligentrobot.

Robots may be classified into industrial, medical, household, militaryrobots and the like according uses or fields. A robot may include anactuator or a driver including a motor to perform various physicaloperations, such as moving a robot joint. In addition, a movable robotmay include a wheel, a brake, a propeller, and the like in a driver torun on the ground or fly in the air through the driver.

The foregoing technical features may be applied to a device supportingextended reality.

Extended reality collectively refers to virtual reality (VR), augmentedreality (AR), and mixed reality (MR). VR technology is a computergraphic technology of providing a real-world object and background onlyin a CG image, AR technology is a computer graphic technology ofproviding a virtual CG image on a real object image, and MR technologyis a computer graphic technology of providing virtual objects mixed andcombined with the real world.

MR technology is similar to AR technology in that a real object and avirtual object are displayed together. However, a virtual object is usedas a supplement to a real object in AR technology, whereas a virtualobject and a real object are used as equal statuses in MR technology.

XR technology may be applied to a head-mount display (HMD), a head-updisplay (HUD), a mobile phone, a tablet PC, a laptop computer, a desktopcomputer, a TV, digital signage, and the like. A device to which XRtechnology is applied may be referred to as an XR device.

The claims recited in the present specification may be combined in avariety of ways. For example, the technical features of the method claimof the present specification may be combined to be implemented as adevice, and the technical features of the device claims of the presentspecification may be combined to be implemented by a method. Inaddition, the technical characteristics of the method claim of thepresent specification and the technical characteristics of the deviceclaim may be combined to be implemented as a device, and the technicalcharacteristics of the method claim of the present specification and thetechnical characteristics of the device claim may be combined to beimplemented by a method.

1. A method in a wireless local area network system, the methodcomprising: transmitting, by a station (STA), a first physical protocoldata unit (PPDU) including a link adaptation control field, wherein thelink adaptation control field includes a bit indicating whether the linkadaptation control field includes information related to low-latencytraffic, and wherein the low-latency traffic is traffic requiring alatency less than or equal to a threshold value; receiving, by the STA,an allocation of a resource for the low-latency traffic; andtransmitting, by the STA via the resource, a second PPDU including thelow-latency traffic.
 2. The method of claim 1, wherein the informationrelated to the low-latency traffic includes at least one of informationrelated to a time point at which the low-latency traffic is stored in abuffer.
 3. The method of claim 1, wherein the information related to thelow-latency traffic includes at least one of information related to atime interval of an uplink trigger based PPDU (UL TB PPDU) andinformation related to a length of a UL TB PPDU.
 4. The method of claim1, wherein the link adaptation control field includes at least one ofinformation on a number of spatial stream (NSS), information on amodulation and coding scheme (MCS), information on a resource unit (RU)allocation, information on bandwidth (BW).
 5. The method of claim 1,wherein the link adaptation control field includes first information orsecond information based on a bit indicating whether to include theinformation related to low-latency traffic, wherein the firstinformation includes at least one of whether dual carrier modulation(DCM) is used, a PPDU format, a coding type, a PPDU sequence, andwhether beamforming is used, and wherein the second information includesat least one of information related to a time point at which thelow-latency traffic is stored in a buffer, information related to a timeinterval of an uplink trigger based PPDU (UL TB PPDU), and informationrelated to a length of a UL TB PPDU.
 6. The method of claim 1, whereinthe low-latency traffic has an access category for the low-latencytraffic.
 7. A station (STA) in a wireless local area network system, theSTA comprises, a transceiver for transmitting and receiving a radiosignal; and a processor coupled to the transceiver, wherein theprocessor is configured to: transmit a first physical protocol data unit(PPDU) including a link adaptation control field, wherein the linkadaptation control field includes a bit indicating whether the linkadaptation control field includes information related to low-latencytraffic, and wherein the low-latency traffic is traffic requiring alatency less than or equal to a threshold value; receive an allocationof a resource for the low-latency traffic; and transmit, via theresource, a second PPDU including the low-latency traffic.
 8. The STA ofclaim 7, wherein the information related to the low-latency trafficincludes at least one of information related to a time point at whichthe low-latency traffic is stored in a buffer.
 9. The STA of claim 7,wherein the information related to the low-latency traffic includes atleast one of information related to a time interval of an uplink triggerbased PPDU (UL TB PPDU) and information related to a length of a UL TBPPDU.
 10. The STA of claim 7, wherein the link adaptation control fieldincludes at least one of information on a number of spatial stream(NSS), information on a modulation and coding scheme (MCS), informationon a resource unit (RU) allocation, information on bandwidth (BW). 11.The STA of claim 7, wherein the link adaptation control field includesfirst information or second information based on a bit indicatingwhether to include the information related to low-latency traffic,wherein the first information includes at least one of whether dualcarrier modulation (DCM) is used, a PPDU format, a coding type, a PPDUsequence, and whether beamforming is used, and wherein the secondinformation includes at least one of information related to a time pointat which the low-latency traffic is stored in a buffer, informationrelated to a time interval of an uplink trigger based PPDU (UL TB PPDU),and information related to a length of a UL TB PPDU.
 12. The STA ofclaim 7, wherein the low-latency traffic has an access category for thelow-latency traffic.
 13. (canceled)
 14. An access point (AP) in awireless local area network system, the AP comprises, a transceiver fortransmitting and receiving a radio signal; and a processor coupled tothe transceiver, wherein the processor is configured to: receive a firstphysical protocol data unit (PPDU) including a link adaptation controlfield, wherein the link adaptation control field includes a bitindicating whether the link adaptation control field includesinformation related to low-latency traffic, and wherein the low-latencytraffic is traffic requiring a latency less than or equal to a thresholdvalue; allocate a resource for the low-latency traffic; and receive, viathe resource, a second PPDU including the low-latency traffic. 15-16.(canceled)